No description provided.
Bug 1558517 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We plan to reformat m-c using Prettier on July 5 before the merge. This bug serves as a place for reviewing a few more preliminary patches required before a format can be done. Prettier was added top level in bug 1556013, smoke tests already carried out with devtools/debugger in bug 1551218. Automatic patch reformatting during rebase is being taken care of in bug 1556328. The full roadmap is available here: https://docs.google.com/document/u/1/d/1qV3aULyhulHsNHvnlbgAxeqlMGnpklUnxmpnY1OovXk Four different competing prettifiers were experimented with earlier this year, carrying out reformats on the entire tree and measuring their impact for every single rule individually on all of m-c. In the end, Prettier was chosen because it was the only tool providing consistency and predictability, along with parsing and integration compatibility with our existing codebase. Out of all the possible configuration options rules, we've also picked the ones that had a measurable minimal code churn, otherwise the default values were kept.
We plan to reformat m-c using Prettier on July 5 before the merge. This bug serves as a place for reviewing a few more preliminary patches required before a format can be done. Prettier was added top level in bug 1556013, smoke tests already carried out with devtools/debugger in bug 1551218. Automatic patch reformatting during rebase is being taken care of in bug 1556328 and bug 1556393 The full roadmap is available here: https://docs.google.com/document/u/1/d/1qV3aULyhulHsNHvnlbgAxeqlMGnpklUnxmpnY1OovXk Four different competing prettifiers were experimented with earlier this year, carrying out reformats on the entire tree and measuring their impact for every single rule individually on all of m-c. In the end, Prettier was chosen because it was the only tool providing consistency and predictability, along with parsing and integration compatibility with our existing codebase. Out of all the possible configuration options rules, we've also picked the ones that had a measurable minimal code churn, otherwise the default values were kept.