You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the markers of type "tracing" don't work too nicely with the new marker schema. "type" should be the differentiator on how we display things. However, these markers use a "category" designation instead. This "category" field in the payload should be migrated to the "type" field.
In the marker schema work, I'm working around this by selecting the type OR the category if the type === "tracing".
Write a front-end upgrader.
Update the front-end schema usage to not have the above mitigation. TODOs
Yeah I'm pretty sure the "category" field was completely ad-hoc. I think these tracing markers can all be identified by their name and the "category" is not worth preserving.
Right now the markers of type "tracing" don't work too nicely with the new marker schema. "type" should be the differentiator on how we display things. However, these markers use a "category" designation instead. This "category" field in the payload should be migrated to the "type" field.
In the marker schema work, I'm working around this by selecting the type OR the category if the
type === "tracing"
.┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: