Add additional documentation for Episode Category / Patient detail template inheritance. #1651
Conversation
This file contains 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
…mplate inheritance. refs #1428
|
so... The links don't work for me
I haven't just fixed them, because I don't really understand why they don't work but the links in for example datamodel.md that point to |
|
created #1651 to turn them into relative paths which we do use elsewhere |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Although the ticket talks about template inheritance in general, this PR adds just docs for the part mentioned.
We could definitely use more x-linkage in the docs, and short term happy to add any clarifying sections for any specific things pointed out.
Medium term, completing the theming tutorial (https://opal.openhealthcare.org.uk/docs/tutorials/theming_tutorial/) and / or drastically reducing the role of Angular makes the 'template inheritance' thing go away by reducing the point of ambiguity over 'what is rendering this bit of screen'.
I think this closes that ticket at least as much as we're reasonably likely to write any extensive template inheritance specific docs (not at all likely) in the short term.
closes #1428