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

Import jest zone patch #214

Merged
merged 24 commits into from
Dec 13, 2018
Merged

Conversation

JLHwung
Copy link
Contributor

@JLHwung JLHwung commented Dec 13, 2018

This PR is addressed to thymikee/jest-zone-patch#9 (comment).

For the sake of complete git history, I merge the commits into this repository.

There is another LICENSE issue: The jest-zone-patch is licensed under BSD-3-Clause while this repository under MIT. I keep the original BSD LICENSE on this PR and left it as-is.

@thymikee
Copy link
Owner

Please change the license to MIT, I used BSD-3 because just because I was more familiar with it at the time :D

Copy link
Owner

@thymikee thymikee left a comment

Choose a reason for hiding this comment

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

Awesome, thank you so much! ❤️

@thymikee thymikee requested review from wtho and ahnpnl December 13, 2018 13:04
@JLHwung
Copy link
Contributor Author

JLHwung commented Dec 13, 2018

@thymikee Technically speaking we should inform every contributor of jest-zone-patch to ask them if they allow to relicense the code under MIT license.

As this PR is not an emergent one, I think we should stick to a relicensing procedure and then we can merge and go forward.

@thymikee
Copy link
Owner

Ok, so we can leave that for now :)

Copy link
Collaborator

@ahnpnl ahnpnl left a comment

Choose a reason for hiding this comment

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

LGTM, thanks 👍 I'll tag this to 7.0.0 too

@ahnpnl ahnpnl modified the milestones: next, 7.0.0 Dec 13, 2018
@JLHwung
Copy link
Contributor Author

JLHwung commented Dec 13, 2018

@thymikee Cool, I will draft an issue on jest-zone-patch to asking allowance from our contributors.

@thymikee
Copy link
Owner

Trying to rebase & merge through GitHub results in conflicts. Are you OK with squashing & merging it? I'm certainly not very interested in the commit history of jest-zone-patch, and it's still gonna be available in the original repository, just archived.

@JLHwung
Copy link
Contributor Author

JLHwung commented Dec 13, 2018

@thymikee rebase and merge might fail on this unusual cases.

Personally I tend to keep the complete history since it helps during git blame. But if you insist on squashing & merging, I am good to go.

@thymikee thymikee merged commit 66987ed into thymikee:master Dec 13, 2018
@thymikee
Copy link
Owner

Thanks!

@JLHwung JLHwung deleted the import-jest-zone-patch branch December 13, 2018 13:33
Copy link
Collaborator

@wtho wtho left a comment

Choose a reason for hiding this comment

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

Great this came in!

thymikee added a commit that referenced this pull request Jan 26, 2019
* origin/master:
  Upgraded ts-jest version. (#219)
  docs: add astTransformers in configuration example (#218)
  feat: Import jest-zone-patch (#214)
  chore: Migrate CI config to CircleCI v2 (#212)
  Transform templateUrl, styleUrls and styles everywhere (#211)
  feat: adjust semver range of jest-zone-patch (#209)
  Adjust CHANGELOG (#208)
@krokofant krokofant mentioned this pull request Apr 7, 2019
thymikee pushed a commit that referenced this pull request Apr 7, 2019
* jest-zone-patch is embeded (#214) as a dependency and should not be mentioned as being installed at the same time as this package is not found in package.json, package-lock.json or yarn.lock - and can be presumed missing.
* @types/jest might not be installed so install it explicitly
* Specify how to avoid karma conflicts (ref #233)
  - Otherwise consumers might get `TypeError: Cannot read property 'prototype' of undefined` while jest processes new angular cli projects
@wtho wtho mentioned this pull request Oct 26, 2019
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants