Skip to content

Integrate rule definition into OSI fields which can be validated by the osi-validator #355

@vkresch

Description

@vkresch

Describe the feature

OSI fields need to comply to rules which should be defined in the comments of OSI messages (see here an example on how to comment on fields with rules) so that the addon osi-validator can validate OSI messages in scenario files and report back errors and warnings which fields excatly don't comply.

Describe the solution you would like

The rules from yaml files should be migrated into the comment section of the OSI fields. The deafult rule defintion for fields would be no rules.

Describe alternatives you have considered

Set up a seperate rule database or just use the yaml files in accordance to OSI structure of messages and fields.

Describe the backwards compatibility

There should be no issue since the default behavior would be that if no rules are defined no rules are applied to the specific field.

Additional context

See more for related issues:
#332

Metadata

Metadata

Assignees

Labels

FeatureRequestProposals which enhance the interface or add additional features.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions