load_data_type_definitions: Accept OptionSet / Enumeration defined via StructureDefinition #1383
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.
See #1381:
On one server, it was observed that OptionSets are defined using a StructureDefinition instead of EnumDefinition as suggested by the standard.
This PR enables load_enums to parse such definitions and create the enum class.
Point of discussion: Since StructureField has no means of specifying the member value, it is inferred from the index of the field within the fields array:
Includes test.
Also tested against Tani Server 2.7.3 -> observed problem is fixed.