News for hackers. Stuff that matters.
Re:A set of best practices for JavaScript projects by underwater on Wednesday July 05, 2017 @05:51AM (#14701078)
A variant I've seen is //TODO(#7362) where the number is a ticket and is enforced by a lint rule.
Re:A set of best practices for JavaScript projects by CTrom on Wednesday July 05, 2017 @10:47AM (#14702784)
This is what I have found to be a great compromise for my team. Some like todos, others want tickets, so we enforce/support both.
Re:A set of best practices for JavaScript projects by jon-wood on Wednesday July 05, 2017 @03:32PM (#14705454)
If it works then great, but that sounds like a way to piss everyone off by forcing them all to do both.
Re:A set of best practices for JavaScript projects by CTrom on Thursday July 06, 2017 @02:11PM (#14712489)
Yeah I find our "TODOs" don't live very long in the code base.
Re:A set of best practices for JavaScript projects by vahidpg on Wednesday July 05, 2017 @09:48AM (#14702343)
That's a great idea
Re:A set of best practices for JavaScript projects by sturmen on Wednesday July 05, 2017 @09:35AM (#14702252)
this guy gets it
Re:A set of best practices for JavaScript projects by marksomnian on Wednesday July 05, 2017 @06:02AM (#14701123)
This is a really good idea.