You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In the hydrolib.core.dflowfm.mdu.models code, all mdu keywords are defined. The comments and keywords+type+default are defined separately, like so:
Describe the solution you'd like
From a maintenance point of view, it would be convenient to define the comments as part of the keyword, for instance by defining a class based on Field, containing an extra comment property. Furthermore (and alternatively), it would be great if all keywords (including type, default, GA/research status, comment and existing/deprecated status) could be moved to a json/csv file instead of being defined in the code. This would be a first step towards aligning the keywords between kernel/hydrolib-core/GUI.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In the
hydrolib.core.dflowfm.mdu.models
code, all mdu keywords are defined. The comments and keywords+type+default are defined separately, like so:HYDROLIB-core/hydrolib/core/dflowfm/mdu/models.py
Lines 45 to 77 in 08b8294
Describe the solution you'd like
From a maintenance point of view, it would be convenient to define the comments as part of the keyword, for instance by defining a class based on
Field
, containing an extra comment property. Furthermore (and alternatively), it would be great if all keywords (including type, default, GA/research status, comment and existing/deprecated status) could be moved to a json/csv file instead of being defined in the code. This would be a first step towards aligning the keywords between kernel/hydrolib-core/GUI.The text was updated successfully, but these errors were encountered: