You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is no concrete way to simplify how URI Templates are used throughout a Hydra application.
First, they are used as create resource identifiers for serialized objects. Currently the only way is to manually use a URI Template to construct the identifier
By introducing a pattern similar to ServiceStack routing, where routing is part of the model it should be possible to simplify handling of URI Templates for routing and creating identifiers.
The BindTemplate would be an extension which looks for IdentifierTemplateAttribute on given instance's type and uses passed params and/or property values to fill in the template.
And finally, the route path wouldn't be needed at all in module
* proof of concept for wikibus/Argolis#4
* move getting template from module and some comments
* make template api injectable
* replace all handling of templates with attributes
* add interfaces and make stuff actually injectable
* make action `Func<object, object>`
* add async variant to argolis module
* make repositories and actions async
* more work on templates
* update with new Argolis packages
* remove spike code
* fix tests to reflect change to template usage
* automatically deploy only on master
* fix appveyor tabs
* less changef for PR
* paket simplify
* paket update
* change routing templates
* code review and removed obsolete stuff
Currently there is no concrete way to simplify how URI Templates are used throughout a Hydra application.
First, they are used as create resource identifiers for serialized objects. Currently the only way is to manually use a URI Template to construct the identifier
Second, the very same template could be used for routing in Nancy. It is what I started implementing in Nancy.Routing.UriTemplates
By introducing a pattern similar to ServiceStack routing, where routing is part of the model it should be possible to simplify handling of URI Templates for routing and creating identifiers.
Something like
The
BindTemplate
would be an extension which looks forIdentifierTemplateAttribute
on given instance's type and uses passed params and/or property values to fill in the template.And finally, the route path wouldn't be needed at all in module
The text was updated successfully, but these errors were encountered: