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(integration): angular 5.2 + typescript 2.7 #852

Merged
merged 20 commits into from
Feb 26, 2019
Merged

Conversation

splincode
Copy link
Member

@splincode splincode commented Feb 18, 2019

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)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

#847

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

@splincode splincode changed the title Integration test test(integration): angular 5.2 + typescript 2.7 Feb 18, 2019
Copy link
Member

@markwhitfeld markwhitfeld left a comment

Choose a reason for hiding this comment

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

Great!

@markwhitfeld
Copy link
Member

markwhitfeld commented Feb 18, 2019

Just a note that, as discussed, Angular 5.2 does officially not support TS 2.7, but there is an existing issue #357 that has been around for a while that points out why we upgraded to TS2.7 as a workaround (at least for now).
Also, upgrading rxjs with the compat lib fixed issue #270 also found in this integration app.

@markwhitfeld
Copy link
Member

@splincode I recommend just adding a 'pre*' npm script step for the specific integration build task that copies the @ngxs folder into the node_modules folder of the ng 5 integration app.
This worked for me and allowed me to identify and fix those issues.

@splincode
Copy link
Member Author

We can't support TypeScript 2.7, because my build does not work at all for the new version of NGXS (3.4.0-dev): ReactiveX/rxjs#4512

I propose to make an announcement where we indicate the versions that we can minimally support.

Minimal TypeScript - 2.8
Minimal Angular - 5.2
Minimal RxJS - 6.2, or (rxjs - 5.6.0-forward-compat.4, rxjs-compat - 6.2.2)

@splincode splincode changed the title test(integration): angular 5.2 + typescript 2.7 test(integration): angular 5.2 + typescript 2.8 Feb 22, 2019
# Conflicts:
#	packages/hmr-plugin/src/public_api.ts
#	packages/hmr-plugin/src/symbols.ts
#	yarn.lock
@splincode
Copy link
Member Author

integration test is ready

NgxsHmrOptions,
NgxsHmrSnapshot,
WebpackModule,
BootstrapModuleFn
Copy link
Member

Choose a reason for hiding this comment

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

Why have WebpackModule and BootstrapModuleFn been added to the exports?
Was something not working? It works fine in my app without this.

Copy link
Member Author

Choose a reason for hiding this comment

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

no, it works without, I just wanted to use the types in the example, the user may also want this

@@ -50,6 +42,6 @@
"protractor": "5.1.2",
"ts-node": "4.1.0",
"tslint": "5.9.1",
"typescript": "2.7.1"
"typescript": "2.8.1"
Copy link
Member

Choose a reason for hiding this comment

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

What was the reason for this version bump?
I had it working with 2.7.1

Copy link
Member Author

Choose a reason for hiding this comment

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

ReactiveX/rxjs#4512 (comment)

I did the same thing, copied the directories, it did not work, I did it through the paths, but it did not work there

@splincode splincode changed the title test(integration): angular 5.2 + typescript 2.8 test(integration): angular 5.2 + typescript 2.7 Feb 24, 2019
@markwhitfeld
Copy link
Member

Giving an error when I try to start this integration app:
image

@splincode
Copy link
Member Author

@markwhitfeld we need fix it

@splincode
Copy link
Member Author

I think we need to add unit tests for this integration test.

@markwhitfeld
Copy link
Member

Ok, I got the router working. Fixed the issue above.
@splincode I agree about some unit tests. Could you add some. I think just a basic AppComponent test that dispatches an action and then checks that it is rendered on the component would suffice.

@markwhitfeld
Copy link
Member

markwhitfeld commented Feb 25, 2019

One last issue I have picked up...
App starts and serves great, but when I made a change and HMR pushed the update then I get this error:
image

@splincode could you try to reproduce and see if there is a bug in HMR? ... maybe HMR doesn't support Angular 5?

Copy link
Member

@markwhitfeld markwhitfeld left a comment

Choose a reason for hiding this comment

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

HMR seems to not be working. See comment above.

@markwhitfeld
Copy link
Member

@splincode will fix the hmr issue with NG5 in a separate PR.

@markwhitfeld markwhitfeld merged commit e6a6632 into master Feb 26, 2019
@eranshmil eranshmil deleted the integration-test branch March 1, 2019 11:03
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