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

fix(ng-add): fix v8 import #189

Merged
merged 2 commits into from
Jan 17, 2020
Merged

fix(ng-add): fix v8 import #189

merged 2 commits into from
Jan 17, 2020

Conversation

jorgeucano
Copy link
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Other... Please describe:

What is the current behavior?

Schematics import wrong version into app.component when you are in angular v8 project

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Copy link
Contributor

@SanderElias SanderElias left a comment

Choose a reason for hiding this comment

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

LGTM

const ngCoreVersionTag = getPackageVersionFromPackageJson(tree, '@angular/core');
let v8 = '';
if (+ngCoreVersionTag.search(/(\^8|~8)/g) === 0) {
v8 = '-8';
Copy link
Contributor

Choose a reason for hiding this comment

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

New version of lib I'm working on is called:
ng-lib-v8 <- notice the v

@jorgeucano jorgeucano merged commit fa173a8 into master Jan 17, 2020
@jorgeucano jorgeucano deleted the schematics/fix-v8 branch January 17, 2020 12:28
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.

2 participants