Tech doc updates metadata (gmtb/develop)#210
Closed
ligiabernardet wants to merge 31 commits into
Closed
Conversation
…se, skip optional and intent attributes for variable/type definitions
…ormat and convert back into old format, currently tested for schemes and module variable definitions, not yet for DDTs
…ct answer when checking logicals
…ype and kind definitions when initializing from a metadata table
…riable names that denote the start of a new variable block
…y: define and export LITERAL, use in logical expressions for array references
…py: add capability to parse variable and type definition metadata tables in new metadata format on a per-file basis
…uard to prevent using multi-dimensional character arrays
…red, this only works if all DDTs are defined in the same file and in the correct order
…tments to convert type/variable definitions and fill in dimensions, array references, ...
…e tables one by one, filling in dimension information from type definitions
…into new_metadata_format_step1_20190725
…20190725 Migrate to new metadata format step 1
…, not for type definitions/module variables
…pment work for generating html table from metadata table
…version of metadata-to-html converter
… to specified output directory
…nk metadata tables
…table plus 'argument table', i.e. 'ozphys_run argument table'
First version of metadata2html converter
…rmat (.meta XML file). Note that while the changes to the files committed here are complete, changes are still needed in other files. Those are in progress.
Collaborator
Author
|
This PR was meant for gmtb/develop, not master. You can close this PR, I do not see how to take it back. I will resubmit to the right place. Tks |
Collaborator
I can't change the base for this one anymore, because you already created a new PR (#211). I will close this PR #210 and reference the discussion/approval in #211. |
Collaborator
|
Superseded by #214 (targeting the correct branch gmtb/develop). |
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
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 contains initial changes to update the documentation to reflect the new metadata format. The changes in the modified files are complete are ready for review. After I receive your feedback on these changes, I will proceed with the changes needed in the other files (that is, other parts of the Technical Documentation).
I do not see how to request a review by @JulieSchramm as her name doe snot appear on the drop down list of potential reviewers. Please advise.