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
{{ message }}
This repository has been archived by the owner on Sep 21, 2018. It is now read-only.
I think that the results of this experiment are in — and it turns out all this kind of tool won't be worth the trouble.
Edge cases and editor plugins pose big problems that could significantly affect the adoption and therefore utility of an all-in-one package like this. The level of standardization is over the top, and the effort required to black-box these tools is kind of insane.
I think we'll get nearly equivalent benefits with less fuss and more flexibility by continuing to focus on eslint-config-mapbox and documentating conventions.
@mapbox/frontend-platform any objections or final reflections?
The text was updated successfully, but these errors were encountered:
Kind of a bummer that the dream has died, but I defer to you judgement on Stickler's future. Focusing on eslint-config-mapbox, documentation, and onboarding folks to conventions seem like very good alternatives and, were we to choose between them and stickler, I think they'd be a more effective use of resources.
I think that the results of this experiment are in — and it turns out all this kind of tool won't be worth the trouble.
Edge cases and editor plugins pose big problems that could significantly affect the adoption and therefore utility of an all-in-one package like this. The level of standardization is over the top, and the effort required to black-box these tools is kind of insane.
I think we'll get nearly equivalent benefits with less fuss and more flexibility by continuing to focus on eslint-config-mapbox and documentating conventions.
@mapbox/frontend-platform any objections or final reflections?
The text was updated successfully, but these errors were encountered: