In case of prettier check failure, it is hard to find out what is the problem (which rule is involved) and where is the problem (which file, which line). So it takes some time to find how to fix the issue, whereas it may be avoided easily:
- display which file is not valid + which rule is violated
More over, the task yarn prettier:format (which can be used to resolve the violation, or not) does not follow the prettier semantic for the same purpose : write. So, this may be time consuming for new dev which already know prettier (very widely used) and is easy to fix:
- rename task
prettier:format to prettier:write.
In case of prettier check failure, it is hard to find out what is the problem (which rule is involved) and where is the problem (which file, which line). So it takes some time to find how to fix the issue, whereas it may be avoided easily:
More over, the task
yarn prettier:format(which can be used to resolve the violation, or not) does not follow the prettier semantic for the same purpose :write. So, this may be time consuming for new dev which already knowprettier(very widely used) and is easy to fix:prettier:formattoprettier:write.