James Stevenson

> Consider also changing the vrs-annotate CLI name to something else like vrsify or something. dangit

Just spitballing -- I'm not sure VRS Python needs to be supporting an expression syntax that isn't defined in VRS. Maybe that dictates a change in VRS, or in VRS-Python.

If this is gonna change to a big "clean up the translator" issue: why is _Translator an ABC?

> Update: Oh wait, this might be a me issue. CNV tests are failing by itself Right, that's the same issue I'm seeing. They seem to only pass if run...

I'm no longer able to replicate this, I think it must've been an error on my end

Oh, wait, I might've found how this happens. Reopening.

@ehclark that's a fair point, it definitely is breaking. What if something like this was an optional flag?

> But as the types of variants supported by VRS expands, that will change. Having a stable interface between our application and VRS ID computation would be preferable. Yeah, maybe...

I believe -- though I could be wrong -- that we are already in conformance with either. We would just want to change language and that should be enough.

@theferrit32 only 5? dream bigger