Traffic Incident Management: CARMA Web UI

[dan-du-car]

PR Details

Description

Add traffic event info panel
Add lane change status panel

Related Issue

Motivation and Context

Traffic Incident use case

How Has This Been Tested?

Types of changes

• Defect fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that cause existing functionality to change)

Checklist:

• I have added any new packages to the sonar-scanner.properties file
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
  CARMA Contributing Guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[maefromm]

@dan-du-car as discussed I can merge this if it makes simpler for you with the conflicts. but the following needs to be addressed: 1) All the messages should match what's in the design document. 2) implement all the messages 3) EVENT REASON should not say "EVENT_REASON" twice. Make use of the mockup to say what we propsoed to the client.
@maefromm
It is removed at this commit
ad44d1f