DerivePartialModel: Allow specification of Entity via a Path in addition to as an Ident #2111
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Info
Content: With the current implementation when deriving
DerivePartialModel
, one must specify theEntity
whose columns should be used as anIdent
- meaning that one must import it into the current scopeThis is somewhat unwieldy, especially when dealing with generated code, where one would prefer to just
use
the containing module, not the contents themselvesThis PR instead allows one to specify a
Path
, meaning that no directuse
is required anymoreTicket: Sorry, should have probably created a ticket first - does not exist atm, but can create one if necessary.
Bug Fixes
Entity
to be specified as aPath
, not just anIdent
, alleviating the need to import the Entity struct whenever you want to use the DerivePartialModel macroBreaking Changes
Path
s are a superset ofIdent
sChanges