Bug-fix: Add range checking for parameters in MetricsReportingConfiguration #148
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.
This PR supercedes #147 by performing range checking for the M1 metrics reporting parameters in autogenerated code (based on modified YAML) rather than explicitly in 5GMS AF code.
This also moves the
TS26512_M1_MetricsReportingProvisioning.yaml
override file back into the rt-common-shared repository (see 5G-MAG/rt-common-shared#36 for counterpart PR) as it is potentially shared between this repository and rt-5gms-application-provider.