Remove unused mitigation_issue field from Development failure initiators section in DFA documentation #2581
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.
Bugfix
Description
mitigation_issueattribute fromfeat_saf_dfa__persistency__execution_blocking, which violates the metamodelpattern
^https://github.com/.*$.This fix is required because
score-docs-as-codenow generates sphinx-needs 6schema definitions (
schemas.json) from the S-CORE metamodel. These schemas areevaluated at parse time on all needs, including those pulled from external
repositories. The empty string
""was previously silently accepted by thePython-based post-build checks but is now correctly rejected by the schema
validation, which enforces that
mitigation_issue, if present, must be a validGitHub URL.
See also: #394
Related ticket
Important
Please replace
[ISSUE-NUMBER]with the issue-number that tracks this bug fix. If there is no suchticket yet, create one via this issue template.
closes #2582 (bugfix ticket)