I have developed a vendetta against poor error messages. I have discovered that validating input like: function isValid(input: string): boolean; Is almost always bad. function getInvalidRange(input: string): undefined | [number, number]; Is way better.
-
-
Show this thread
-
What does that actually mean? Actually pointing to the specific range and location of invalid input rather than "there is an error in here somewhere".
Show this thread -
Rome ingests package.json files and performs some normalization and validation. One of the fields is name. When you use a package.json name in npm or yarn that is invalid, it will just yell at you. Rome points to the exact location with some possible hints. Examples:
Show this thread -
-
-
These errors aren't generated until after either. The validation logic actually does some rough "autofixing". It would be possible to have a flag that suppresses the errors and writes the normalized fixed version to disk. Super nuanced and hard UX though to implement.
Show this thread
End of conversation
New conversation -
-
-
Trying to make this not a “so when are you releasing it” because I’m sure you get a million of those. That being said, any idea of plans for Rome? Seems so cool, keep up the good work!
-
It's not in production usage anywhere. That is generally the bar for open source then there's more long term commitment for the project. Or if the project is scrapped (ie. no internal support), hopefully unlikely, then that's another open source initiator.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 