docs: improve documentation for copy directives #36
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
As of now it is unclear how copy directives are supposed to work. This commit improves the description, although there are still many under-specified aspects to be addressed later on. Signed-off-by: Silvano Cirujano Cuesta <[email protected]>
Silvanoc
force-pushed
the
improve-documentation-copy
branch
from
51ebcc6 to
0164002
Compare
Update the transformer model python datamodel according the latest changes in the model itself. Signed-off-by: Silvano Cirujano Cuesta <[email protected]>
cmungall
approved these changes
Aug 7, 2024
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.
As of now it is unclear how copy directives are supposed to work.
This PR makes a proposal to improve the documentation directly on the transformation model descriptions, but without changing the specification itself.
Reviewers are requested to confirm/correct the assumptions that brought me to the documented understanding. The mentioned and hereby documented assumptions have been portrayed in the implementation draft available in #35.
There are still many under-specified aspects to be addressed later on.