he/him 
I haven't posted anything about Rome in a while so here is what I worked on this evening. These are more error messages. It's obviously not all I'm working on but it's the easiest thing to tweet and discuss.
Show this thread
-
No, I get that. My question was more around the multitude of possible errors. I imagine there's a separate module for every single test, so how will maintainers know that the validator they want to add exists already? Documentation discipline? Kinda reminds me of ESLint rules.
The validation and normalization is the same code. I don't really understand the question. There isnt some special set of validators.
-
-
I mean "Redundant @ in org name" is one highly specific assertion. I assume there are going to be *tons* like that soon, so my concern is around organizing them and keeping them discoverable. To be clear, I'm totally not saying specificity is a bad thing.
-
The validation rules aren't in separate files or even functions. The validation and normalization code is the same and everything is collocated. This is a weird case because it deals with offsets and uses a 0/1-indexed safe library.https://gist.github.com/sebmck/d601cf29070212a4b75862c9e3e0247b …
- 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.