noi-techpark / it.bz.opendatahub.databrowser

Explore and navigate through Open Data you need to build your next service.
https://databrowser.opendatahub.com
GNU Affero General Public License v3.0
9 stars 7 forks source link

Fix prettier linting for windows #390

Closed henri-egger closed 1 year ago

henri-egger commented 1 year ago

While adapting the husky pre-commit-hook for windows i noticed that it wouldn't even have been possible for any windows user to commit as prettier doesn't allow crlf end of lines.

I just added a rule to the .eslintrc.json file to allow for those kinds of line endings.

gappc commented 1 year ago

@henri-egger thank you for your PR, here are my comments:

As a side node: at the moment we have contributors that use Windows, so it seems to be possible to commit from Windows, maybe you mentioned something different?

henri-egger commented 1 year ago

@gappc yes the reuse commits are put in by accident, i will provide a new clean PR once we have decided on a solution.

According to the official Prettier documentation, it would actually make more sense to create a .gitattributes file containing * text=auto eol=lf. I tried it however, following the exact steps mentioned here and couldn't get this solution to work.

You mentioned there are already Widows users working on the project, i believe however that they are using WSL as that is very common for Windows users doing web development, can you confirm this? Also i tried doing a clean clone of the repo on Windows without wsl and i was not able to commit due to the prettier linting, so even if some people are already working on Windows which might have found a personal solution, new Windows contributors still have this problem.

gappc commented 1 year ago

@henri-egger thank you for the feedback.

You mentioned, that the .gitattributes solution did not work, what was the problem? Reading through the link you provided, it seems that the line-ending problem should be solvable by these configurations. It would be great if you could take a second look at it.

If I may ask you another favor: could you please put your comments and current knowledge (problems, solutions, links) regarding the line-ending problem from this PR to issue #390 such that we can keep discussing there? I think that would be the appropriate place and the info won't get lost. Thx :)

henri-egger commented 1 year ago

@gappc i will try to take a closer look and move the discussion, did you mean to link issue #345 or would you like me to create a new issue #390?