(Best way to) Avoid ragged error annotations on graph

[cmalinmayor]

Description

We want to annotate the NodeFlags and EdgeFlags on all nodes/edges. The CTC errors currently do this, but the divisions do not. We need to determine where to first set all Flags to a default value - TrackingGraph initialization, or start of error annotation. And then implement the solution and add documentation.

Topics

What types of changes are you suggesting? Put an x in the boxes that apply.

• New feature or enhancement
• Documentation update
• Tests and benchmarks
• Maintenance (e.g. dependencies, CI, releases, etc.)

Which topics does your change affect? Put an x in the boxes that apply.

• Loaders
• Matchers
• Track Errors
• Metrics
• Core functionality (e.g. TrackingGraph, run_metrics, cli, etc.)

Priority

• This is an essential feature
• Nice to have
• Future idea

Are you interested in contributing?

• Yes! 🎉
• No 🙁

[msschwartz21]

At the beginning of the error class, all nodes/edges should have all flags applied with the default value. As cases are examined the value should be flipped accordingly.

Caroline and I went back and forth on this, but for now I think we are going to continue with ragged annotations until a use case emerges that will break with ragged annotations. In the meantime, we will improve documentation about the flags so that it is clear what a missing flag means.