Uses Iri as NamedNode value and allow individual article retrieval #184
Conversation
nlisgo
changed the title
|
If someone edits the description of an issue you have created, your spirit will be evoked. |
|
Now that merge of #181 is possible, should be rebased to remove the changes that are already in. |
…s-dereferenceable-cont # Conflicts: # src/routes/add-article.ts
…s-dereferenceable-cont
Co-Authored-By: Chris Wilkinson <c.wilkinson@elifesciences.org>
|
I've pushed 0d43a9a which does contradict #184 (comment). There's complexity in the article 'route' having to know whether to lookup or not (could be extracted though), and the dependency cycle (#184 (comment); again could be solved by extracting). Not 100% happy with this, means having to add another route if the format is ever changed. Will continue to think. |
Happy to kick this problem down the road. We don't need to solve it now. |
|
Think this is all good now, just need to resolve/bypass the Hypertest problem. |
|
hypermedia-app/hydra-validator#57 should fix Hypertest. |
This is a followup to: #181
It uses an Iri as the NamedNode value and allwos the retrieval of an individual article.