Skip to content
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

#226: Add support for rtc files #342

Draft
wants to merge 22 commits into
base: main
Choose a base branch
from
Draft

Conversation

priscavdsluis
Copy link
Contributor

@priscavdsluis priscavdsluis commented Sep 23, 2022

In this branch I am experimenting a little bit with the RTC XSD files.
With XMLSpy, I converted each XSD to a JSON schema:
image

In the same window (but maybe this is not really a necessary step):

Namespaces...: update Deltares namespaces (such as rtc and fews) to a placeholder like "PLACEHOLDER" (this will make it easier to remove the namespaces from the JSON schema)

In each generated JSON schema then replace :PLACEHOLDER and PLACEHOLDER: with an empty string to remove them.

Attributes from XSD are converted to a property in JSON with a @ prefix. Converting this to python will result in a private field. So we need to replace it. In each generated JSON replace "@ with "attr_.

pip install datamodel-code-generator

Example for rtcDataConfig.json:
datamodel-codegen --input rtcDataConfig.json --input-file-type jsonschema --output . --field-constraints --allow-population-by-field-name --use-subclass-enum --use-schema-description

This command will create some python files.

For each RTC file a folder was created in the repository:
hydrolib.core.io.rtc.rtcDataConfig
hydrolib.core.io.rtc.rtcToolsConfig
hydrolib.core.io.rtc.rtcRunimeConfig
etc.

In each folder a generated folder is added.
In here the generated files should be stored.
In models.py we should put the Model that the user will use directly.
This Model will use the generated files under the hood.

In the rtcDataConfig folder a parser and a serializer have been added to create a prototype for reading and writing logic.
Most of the implementation can be used for the other rtc models as well I expect.
I think it would also be a good to add a layer between the generated models and the xml (de)serialization in the final implementation.

Unfortunately the rtcToolsConfig is not converted to valid python code, because the name of a module conflicts with the name of a class: TimeSeriesSimpleType and ExternalParameterSimpleType

It would also be nice if we could fully automate it (I am not sure yet if this is possible with XML Spy).

@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot E 24 Security Hotspots
Code Smell A 1015 Code Smells

No Coverage information No Coverage information
7.3% 7.3% Duplication

@priscavdsluis priscavdsluis linked an issue Oct 3, 2022 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RTC input files support
2 participants