6 ms·
It works as it should, as a user you have to accept that rome works in a specific way. If you can do that and live with that, rome is a excellent tool. It took
by progx 3y ago
It works as it should, as a user you have to accept that rome works in a specific way.
If you can do that and live with that, rome is a excellent tool. It took me some weeks to accept the "rome way" and now i am more than happy with that and did not waste time with endless configurations of eslint/prettier.
- Raed667 3y agoWhen you have a large project with +500k lines of code, two dozen contributors, tens of eslint rules, it is very hard to "just" do it the rome way. A migration path is required, otherwise you'll introduce a tool, have a PR that reformats everything and it will be a huge mess.
- conaclos 3y agoRome is less opinionated than it used to be. However, I admit it is still more opinionated than ESLint. It is part of its ADN. However, Rome is also trying to provide a smooth experience. And we are open to relax some rules if it makes sense. If you have some time, we would like to get to know the rough edges of Rome.
- campers 3y agoAfter you commit that big PR add the commit hash to the .git-blame-ignore-revs file. Then it won't affect the git blame attributions. https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view https://docs.github.com/en/repositories/working-with-files/u...