Epic / Locatability

[dncsvr]

Improve domain objects locating in baked.

Tasks

• ID Configuration as Feature
  • Issue / Locatability / ID Configuration As Feature #421
• ID Property
  • Issue / Locatability / Locator System #433
• Locator System
  • Issue / Locatability / Locator System #433
• Nested Locatables
  • Introduce a way to accept a locatable object in a nested records.
  • 🤔 json serialization might be an easier solution here. when
    serializing serialize as is. when deserializing expect only id
  • in req/res body

    {
      "entity": { "id": "123" }
    }

  • in request body it is always only prop: { id: ... }, so consider creating
    an object ref dto
    • unique props will NOT be used in object locating
  • 🤔 in response body do not serialize when db object is not loaded
    and is only proxy with id
  • in query string it should be entityId= (it probably already is)
  • id is used as an example, it should use whatever prop name is the domain
    object's id prop. if it is Uid it should be /{uid}, entityUid= and { "uid": ... } in route, query and body respectively
• Issues
  • Refactor OrmConfig Orm to improve design, currently it seems irrelevant
  • Improve Id design
    • factory methods to create id
      • Id.Parse(3) -> this is not parsing -> Id.Create(3)
    • generate to use guid new
    • improve struct to implement other value type interfaces (comparable?)
    • provide id.IsEmpty and Id.Empty
    • consider implicit and explicit cast operators from and to string
      respectively
  • Fix RotingEntitySubclasses fixture
  • Remove SingleByUniqueAttirbute and fix build

Additional Tasks

• Fixes Auto Unique Index #377