[Code health] Consistent naming of local DB converters
See original GitHub issuePretty much every local db entity has to/from conversion methods for converting a corresponding model object to the local db entity type. However, we don’t name these consistently. Sometimes they are named toModel
, sometimes toObject
sometimes to<ModelTypeName>
…
We should pick a consistent naming scheme. For extra clarity, my vote goes toward to<ModelTypeNameModel>Model
; e.g.
toLocationOfInterestModel
; fromLocationOfInterestModel
; toAuditInfoModel
; fromAuditInfoModel
Issue Analytics
- State:
- Created a year ago
- Comments:16 (11 by maintainers)
Top Results From Across the Web
Database Naming Standards - DEV Community
There's long been a huge debate amongst experts in database theory about whether or not database tables should be singular ( customer )...
Read more >9. Naming Conventions - Oracle
Interface names should be capitalized like class names. Methods should be verbs, in mixed case with the first letter lowercase, with the first...
Read more >BI Database Naming Standards: Contents
A naming standard is a collection of rules, which, when applied to data, results in a set of data objects named in a...
Read more >Implement Best Practices for Development - Mendix Docs
This document can be used as a guideline for adopting consistent naming and modeling conventions while developing your Mendix applications.
Read more >Database Engine events and errors - SQL Server
Consult this MSSQL error code list to find explanations for error ... Check the network address name and that the ports for the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think that makes sense. I haven’t made up my mind about using inheritance solely for the purpose of enforcing naming conventions (ie
LocalDbConverter
would never be referenced except by implementors), but the pattern make sense.Nit: Following Java naming conventions (assuming they’re the same in Kotlin) here we’d have
LocalDb
and notLocalDB
.Thanks for working through this!
The last proposal sgtm, all things considered.
On Fri, Sep 23, 2022, 11:35 AM Scott Olsen @.***> wrote: