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

test: fix ts api guardian and public guard tests on windows #30105

Closed
wants to merge 3 commits into from
Closed

test: fix ts api guardian and public guard tests on windows #30105

wants to merge 3 commits into from

Conversation

alan-agius4
Copy link
Contributor

This change addresses several issues with ts-api-guardian and public api guards related tests in Windows

The fixes contain 3 main changes:

  1. In stripExportPattern - replace ^ with ^^^^ in RegExp due to a double escaping requirment under Windows. Note that under Linux this the extra character has no effect because it's still a valid RegExp in Js.
  1. Force *.patch files to always be with a LF line sequence instead of CRLF in windows

  2. When adding JSDoc comments consider the presence of a carriage return in a line new feed

Partially addresses #29785

@alan-agius4 alan-agius4 added the area: build & ci Related the build and CI infrastructure of the project label Apr 25, 2019
@ngbot ngbot bot added this to the needsTriage milestone Apr 25, 2019
@alan-agius4 alan-agius4 added hotlist: windows-support target: patch This PR is targeted for the next patch release labels Apr 25, 2019
This change addresses several issues with ts-api-guardian and public api guards related tests in Windows

The fixes contain 3 main changes:
1) In `stripExportPattern` - replace `^` with `^^^^`  in RegExp due to a double escaping requirment under Windows. Note that under Linux this the extra character has no effect because it's still a valid RegExp in Js.

2. Force `*.patch` files to always be with a LF line sequence instead of CRLF in windows

3. When adding JSDoc comments consider the presence of a carriage return in a line new feed

Partially addresses #29785
@alan-agius4 alan-agius4 marked this pull request as ready for review April 25, 2019 08:42
@alan-agius4 alan-agius4 requested a review from a team as a code owner April 25, 2019 08:42
@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label Apr 25, 2019
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

👍

@alan-agius4 alan-agius4 removed the action: merge The PR is ready for merge by the caretaker label Apr 26, 2019
…talled

When the workspace node_modules are not installed outside of bazel context the api guardian tests fails because the tree artifacts files are not symlinked in windows.

We need to pass the node module location in the node_path
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker comp: ts-api-guardian labels Apr 26, 2019
@AndrewKushnir AndrewKushnir added target: major This PR is targeted for the next major release target: patch This PR is targeted for the next patch release and removed target: patch This PR is targeted for the next patch release target: major This PR is targeted for the next major release labels Apr 26, 2019
AndrewKushnir pushed a commit that referenced this pull request Apr 26, 2019
This change addresses several issues with ts-api-guardian and public api guards related tests in Windows

The fixes contain 3 main changes:
1) In `stripExportPattern` - replace `^` with `^^^^`  in RegExp due to a double escaping requirment under Windows. Note that under Linux this the extra character has no effect because it's still a valid RegExp in Js.

2. Force `*.patch` files to always be with a LF line sequence instead of CRLF in windows

3. When adding JSDoc comments consider the presence of a carriage return in a line new feed

Partially addresses #29785

PR Close #30105
AndrewKushnir pushed a commit that referenced this pull request Apr 26, 2019
…talled (#30105)

When the workspace node_modules are not installed outside of bazel context the api guardian tests fails because the tree artifacts files are not symlinked in windows.

We need to pass the node module location in the node_path

PR Close #30105
AndrewKushnir pushed a commit that referenced this pull request Apr 26, 2019
…talled (#30105)

When the workspace node_modules are not installed outside of bazel context the api guardian tests fails because the tree artifacts files are not symlinked in windows.

We need to pass the node module location in the node_path

PR Close #30105
@alan-agius4 alan-agius4 deleted the windows-fix-tests-guardian branch April 27, 2019 05:37
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
…30105)

This change addresses several issues with ts-api-guardian and public api guards related tests in Windows

The fixes contain 3 main changes:
1) In `stripExportPattern` - replace `^` with `^^^^`  in RegExp due to a double escaping requirment under Windows. Note that under Linux this the extra character has no effect because it's still a valid RegExp in Js.

2. Force `*.patch` files to always be with a LF line sequence instead of CRLF in windows

3. When adding JSDoc comments consider the presence of a carriage return in a line new feed

Partially addresses angular#29785

PR Close angular#30105
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
…talled (angular#30105)

When the workspace node_modules are not installed outside of bazel context the api guardian tests fails because the tree artifacts files are not symlinked in windows.

We need to pass the node module location in the node_path

PR Close angular#30105
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project cla: yes target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants