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
If you have a project with 10s of constraints and you see a failure, it's difficult to tell which constraint was the one causing the failure. You have to read through all the constraints again (and try to remember prolog which you only write in for yarn constraints 😄 ). Having some sort of label/identifier would be helpful.
I know there are plans to rewrite constraints in typescript, in that case, I'd like to extend the feature request to that new system.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If you have a project with 10s of constraints and you see a failure, it's difficult to tell which constraint was the one causing the failure. You have to read through all the constraints again (and try to remember prolog which you only write in for yarn constraints 😄 ). Having some sort of label/identifier would be helpful.
I know there are plans to rewrite constraints in typescript, in that case, I'd like to extend the feature request to that new system.
Beta Was this translation helpful? Give feedback.
All reactions