Clarify example by incrementing version of updated document #51
Conversation
This file contains hidden or 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
Signed-off-by: RingoDev <thomas.grininger@ringodev.com>
|
I've done everything, the last code, then I'll do it, and that's it, I've already done the first two codes. |
puerco
approved these changes
Jan 16, 2026
Member
puerco
left a comment
puerco
left a comment
There was a problem hiding this comment.
Hey sorry this PR went unnoticed @RingoDev. I've read the changes you are proposing, and it makes sense to update the existing example. The current openvex code in the document shows the mechanics of the date bump and inheritance correctly, but it is not really updating the document as the text implies. This fixes it.
Thanks for cathing this!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This is a PR dealing with the documentation inconsistency I raised in #50