Skip to content

Fix duplicate incidentId problem in loggingservice.yaml per STA-010.3b#19

Open
mlsmith1 wants to merge 1 commit intoNENA911:mainfrom
mlsmith1:mlsmith1-fix-dup-incidentId-for-STA-010.3b
Open

Fix duplicate incidentId problem in loggingservice.yaml per STA-010.3b#19
mlsmith1 wants to merge 1 commit intoNENA911:mainfrom
mlsmith1:mlsmith1-fix-dup-incidentId-for-STA-010.3b

Conversation

@mlsmith1
Copy link

STA-0103b fixed the duplicate incidentId problem in the text, but the yaml was never corrected. This version corrects the yaml:

  1. bumped version to 1.2.2 (adjust as needed when merging)
  2. Removed duplicate incidentId from IncidentMergeLogEvent, IncidentUnmergeLogEvent, IncidentLinkLogEvent, and IncidentUnLinkLogEvent.
  3. Made the names match STA-010.3b for the members that represent the second incident id in these LogEvents.
  4. Corrected the camel case of "IncidentIdunlinkedFrom", changed it to "IncidentIdUnLinkedFrom". Should be fixed in 3b text too.
  5. DID NOT modify IncidentSplitLogEvent, which also has the duplicate incidentId problem, because the text in 3b doesn't specify a new name for the second incident id - that erratum must be submitted for STA-010.3f.

1. Removed duplicate incidentId in IncidentMergeLogEvent, IncidentUnmergeLogEvent, IncidentLinkLogEvent, and the IncidentUnLinkLogEvent.
2. Made the names match STA-010.3b for the members that represent the second incident id in these LogEvents. Corrected the camel case of "IncidentIdunlinkedFrom", changed it to "IncidentIdUnLinkedFrom". Must be fixed in 3b text.
3. DID NOT edit IncidentSplitLogEvent, which also has the duplicate incidentId problem, because the text in 3b doesn't specify a new name for the second incident id.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments