Skip to content

Nativescript angular 4.4.x#138

Merged
PeterStaev merged 5 commits intoPeterStaev:masterfrom
jogboms:nativescript-angular-4.4.x
Oct 22, 2017
Merged

Nativescript angular 4.4.x#138
PeterStaev merged 5 commits intoPeterStaev:masterfrom
jogboms:nativescript-angular-4.4.x

Conversation

@jogboms
Copy link
Copy Markdown
Contributor

@jogboms jogboms commented Oct 12, 2017

No description provided.

@PeterStaev
Copy link
Copy Markdown
Owner

Hey @jogboms , thanks for your contribution! I have couple of questions - do we really need to update peer-deps for TNS to be 3.3 at least? I don't see anything in the change log for 3.3 that mentioned Angular 4.4. Cant we just update the Angular deps and nativescript-angular module?

@jogboms
Copy link
Copy Markdown
Contributor Author

jogboms commented Oct 12, 2017

@PeterStaev that's true. I couldn't find one of @vakrilov's comment where he said something about a bug being fixed on the @next branch of tns-core-modules that fixes a bug in v4.4.

Comment thread demo-ng/package.json Outdated
"reflect-metadata": "~0.1.8",
"rxjs": "~5.2.0",
"tns-core-modules": "3.2.0",
"tns-core-modules": "next",
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Can this remain at 3.2.0? Or is it required to have vNext?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Very well. Personally, i just prefer having next builds in development so i could tell if things will break before hand.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Yes, but @next build are very unstable. There could be some TNS problem that would cause the CI builds to fail (like it failed with your first set of changes). So I prefer to stay on the stable versions. Thanks!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes. True. Wondered why it failed too.

Comment thread package.json

"peerDependencies": {
"tns-core-modules": "^3.0.0"
"tns-core-modules": "^3.1.0 || >3.3.0-"
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Again are we using something special from 3.1+? It is best this to remain at 3.0.0 as long as it works with the new new angular.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

nativescript-angular used the same as peer dependency.

Comment thread package.json Outdated
"grunt-exec": "2.0.0",
"nativescript-angular": "4.4.0",
"rxjs": "~5.0.1",
"tns-core-modules": "next",
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Similar thing as above. I prefer this to remain at the least supported version so unless it needs anything from newer modules this should remain at 3.0.1.

@vakrilov
Copy link
Copy Markdown

@jogboms Nice PR!
I believe this is the issue you are talking about (NativeScript/nativescript-angular#992). It will be fixed in the tns-core-modules. It is not related to the nativescript-angular/value-accessors/base-value-accessor fix you did here though.

@jogboms
Copy link
Copy Markdown
Contributor Author

jogboms commented Oct 12, 2017

Couldn't tell for sure what bug it was, only remembered there was one. 😊

@PeterStaev PeterStaev added this to the 3.2.0 milestone Oct 14, 2017
@PeterStaev PeterStaev merged commit 995ff81 into PeterStaev:master Oct 22, 2017
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.

3 participants