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

feat(all): upgrade Angular to v10 #1229

Closed
wants to merge 79 commits into from
Closed

Conversation

griest024
Copy link
Member

@griest024 griest024 commented Jan 12, 2021

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] 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?

Fixes: N/A

What is the new behavior?

Does this PR introduce a breaking change?

[x] Yes
[ ] No

Other information

@damienwebdev damienwebdev mentioned this pull request Jan 12, 2021
3 tasks
@griest024 griest024 changed the title Ng10 2 feat(all): upgrade Angular to v10 Jan 12, 2021
@griest024 griest024 force-pushed the ng10-2 branch 2 times, most recently from 8407696 to a955ae6 Compare January 12, 2021 19:36
@griest024 griest024 marked this pull request as ready for review January 12, 2021 20:43
@griest024 griest024 requested review from a team as code owners January 12, 2021 20:43
@griest024
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@griest024 griest024 force-pushed the ng10-2 branch 6 times, most recently from abb3d9d to dd26e20 Compare January 14, 2021 23:01
@lderrickable
Copy link
Contributor

lgtm

lderrickable
lderrickable previously approved these changes Jan 16, 2021
damienwebdev pushed a commit that referenced this pull request Jan 20, 2021
damienwebdev pushed a commit that referenced this pull request Jan 20, 2021
__typename must be grabbed in order to properly match fragments
`addTypename: true` with the cache forces flushed responses to match the query (which includes __typename)
flushed responses that do not have __typename will cause invariant errors
adding __typename on the response models makes it easier to stub out response objects in tests
damienwebdev pushed a commit that referenced this pull request Jan 20, 2021
@damienwebdev
Copy link
Member

damienwebdev commented Jan 20, 2021

Merged manually with a rebase to 16c7106.

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.

None yet

3 participants