Issue / Locatability / Nested Locatables

[cihandeniz]

Introduce a way to accept a locatable object in a nested records.

Tasks

• Add data class, property model and the code template reverted
• Init data classes reverted
• Revert dto generation
• Implement a prototype json serialization
• Configure serialization of entities to render Id and Label properties
  for their parent entities
  • NonEntity > Child > Parent: non entity and child is full, parent is ref
  • Child > Parent: child is full, parent is ref
  • NonEntity > Entity: both are full
  • this means an entity is ref only when it is under another entity
  • which leads to, entity property of another entity should be ref
  • that's the only rule
  • Child > NonEntity > Parent: all are full
• Configure converter of entity properties to locate using Id properties
  • any entity is converted using IQueryContext
  • 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
  • remove entityId and richTransientId configurations all together, and
    use type replacement for input requests
  • in query string parameter should be entityId= (it probably already is)
• Merge from epic/locatability
• Migrate to the new locator system
• Issues
  • Swagger will render input/output incorrectly, consider fixing this using
    filters...
  • Consider creating proxies for locatables and then initializing them using
    await within controllers and set the actual values to the dto if possible
    • place all locatables in a list under request scope, and load all before
      taking any action
    • create target using _newRichTransient() but postpone await richTransient.With(id)
    • load proxy from nhibernate using _session.Load<Entity>() and load using
      NHibernateUtil.Initialize(entity);