Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Node tests to TypeScript #958

Merged
merged 4 commits into from
Nov 21, 2022
Merged

Migrate Node tests to TypeScript #958

merged 4 commits into from
Nov 21, 2022

Conversation

ibc
Copy link
Member

@ibc ibc commented Nov 20, 2022

NOTE: Had to move node/tests folder to node/src/tests since otherwise compiled JS would be in node/lib/src which is ugly.

*NOTE:* Had to move `node/tests` folder to `node/src/tests` since otherwise compiled JS would be in `node/lib/src` which is ugly.
@ibc ibc requested a review from jmillan November 20, 2022 23:57
@ibc ibc merged commit 605893b into v3 Nov 21, 2022
@ibc ibc deleted the migrate-node-tests-to-typescript branch November 21, 2022 10:42
@@ -59,7 +64,7 @@ const eslintConfig =
}
],
'keyword-spacing' : 2,
'linebreak-style' : [ 2, 'unix' ],
'linebreak-style' : [ 2, isWindows ? 'windows' : 'unix' ],
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why would it depend on OS thought? This will mean people contributing from different operating systems having different code style that either passes Windows CI or *nix CI.

Copy link
Member Author

@ibc ibc Feb 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was for CI lint pass on Windows.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then it doesn't really make sense to me. Why would we want to check for different line breaks depending on OS check is running on?

Copy link
Member Author

@ibc ibc Feb 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty sure that line endings change in place from LF to CRLF when fetching the git repo on Windows. AFAIR that could be a feature of git. Probably it can be disabled.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, I recall something like that too... Okay, thanks for clarifying.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here: https://stackoverflow.com/questions/21822650/disable-git-eol-conversions

AFAIU it's a local setting so we cannot force the Windows machine in GH CI to behave as we would wish.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, it is fine then, thanks!

piranna pushed a commit to dyte-in/mediasoup that referenced this pull request Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants