Issue / Locatability / Locator System #433
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- rename id tests to `ConfiguringEntityIds `
cihandeniz
reviewed
Jan 22, 2026
| that property to entity id route parameter so that entites can be found through | ||
| unique properties as well as their ids. For instance, if entity has | ||
| `SingleByName` then its id route parameter is updated from `{id}` to | ||
| `{idOrName}`. |
Member
There was a problem hiding this comment.
note: remove this coding style from docs, it was removed from code. remove also from recipes
cihandeniz
reviewed
Jan 22, 2026
| { | ||
| features.Add(new Playground.Override.DataAccess.MappingsDataAccessOverrideFeature()); | ||
| features.Add(new Playground.Override.Domain.CustomAttributeDomainOverrideFeature()); | ||
| features.Add(new Playground.Override.Id.MapingIdsOverrideFeature()); |
Member
There was a problem hiding this comment.
overrides are related to Layers, not features or coding styles. so this should bi under DataAccess. i think MappingDataAccessOverrideFeature exists exactly for overrides like this.
- reanem feature to `TransientBinding` - refactor rich transient and entity to configure Locatable attribute - temporarily remove entity subclass samples
… !!! BUILD FAILING !!!
- implement service adde template for adding locators - add additional conventions for entity sub class to fix route and parameter - fix locator adder template - minor edits and refactoring
- remove commented code
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Provide a solution for improving locating transients and entities
Notes
inherit all there is from Rich Transient, and add lookup and nhibernate init
logic.
become locatable, and all query apis, not because they are entities, because
they are rich transients.
Tasks
TransientBinding🤔Locatableattribute when exists otherwise useInitializerfor target andparameter lookup
Locatableotherwise add initializer paramsto query
ILocator<>interfaceRichTransientfeature to configureLocatableattribute andEntityLocator<>implementation forRichEntityRichEntityfeature to configureLocatableattributeLocatorimplementations forRichTransientEntitySubclassViaCompositionto configureLocatableattributeAdditional Tasks
Guid, assignedstringand auto-incrementuintoptions
Id, convention will look for aproperty with a type that is assignable to an id interface such as
IIdId