New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lutaml_uml_datamodel_description macro #34
Comments
…code to read and serialize xmi file, use liquid includes from gem, insert predefined code blocks from macro, test.xmi test file
I think at the current point we can use a YAML file like this: packages:
# includes these packages
- "Package *"
- two*
- three
# skips these packages
- skip: four
|
@ronaldtse implemented in #35 |
…n` macro documentation
…code to read and serialize xmi file, use liquid includes from gem, insert predefined code blocks from macro, test.xmi test file
…n` macro documentation
Implement support for xmi file diagrams lookup. Example of diagram ref in requirement file - https://raw.githubusercontent.com/metanorma/ogc-dggs-xmi/feature/lutaml_uml_datamodel_description/sources/as21-dggs/requirements/_temporal_geometry_and_topology.adoc?token=AAI2XFBA62KNW4HLX5A6GXLBCEDPW. Proposed syntax:
Eg: use diagram name as a lookup id and transform it into <<figure-{{ diagram.xmi_id}}>>(EA names diagram images by this pattern) |
For the record with @w00lf we've also discussed:
|
…n` macro documentation
…up by package and diagram names. Support for mutiply internal diagrams lutaml_datamodel_description macro, fixes
…ure inline macro, specs
This is implemented. Thanks @w00lf . |
…n` macro documentation
We need to create a new macro for generating datamodel ascidoc code similar to the one used in metanorma/ogc-citygml-xmi#1 in lutaml macro. Proposed format:
Where:
/path/to/file.xmi
- required, path to uml datamodel xmi file/path/to/config.yml
- optional, path to special yaml config file, look below for format.preface
,.footer
macroses - optional, sets predefined text to be inserted into the temaplte during render,.preface
and.footer
is just an example of naming, TODO: define actual blocksThe above-mentioned macro need to use supplied xmi file and generate adoc code similar to the one used here - https://github.com/metanorma/ogc-citygml-xmi/blob/master/sources/standard/_packages.liquid and insert into the document.
Yaml config file.
Additional config file used to tell the parser what packages to use in the render and in what order, also it can hold packages to skip.
example:
packages_to_render
- main attribute, need to be a list of string/objects. Each string interpreted as a pattern that will be used to select packages can have a wildcard -*
in order to match multiply packages. In order to skip some packages one can use an object instead of a string:skip: three*
, each object will be taken and matched against package name and if pattern matches it will skip it.The text was updated successfully, but these errors were encountered: