Makes Elements in Contents' Enumerations Referable #892
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
…kes individual "items" in Contents Enumerations referable. Adds noRefs and noRefsLT as convenience functions to make a list of ListTuples without being referable. Updated examples accordingly.
JacquesCarette
approved these changes
Jul 22, 2018
|
Merging this was mildly tricky -- there is a real chance I made a mistake. @Mornix please double-check! |
|
Yup! The merge looks good to me. |
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.
This PR is part of #562. It's a followup to #845 by adding support to
Contents'Enumerationto make individual items referable. It "connects" the references inContentsto those inLayoutObj. Currently, nothing usesEnumerationreferences and all examples have been updated using the convenience functionsnoRefsandnoRefsLTto maintain current behaviour.