Skip to content

chore(apollo): upgrade apollo client dependencies#2916

Closed
erikwrede wants to merge 2 commits intonestjs:masterfrom
erikwrede:master
Closed

chore(apollo): upgrade apollo client dependencies#2916
erikwrede wants to merge 2 commits intonestjs:masterfrom
erikwrede:master

Conversation

@erikwrede
Copy link
Copy Markdown
Contributor

@erikwrede erikwrede commented Jul 11, 2023

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
  • Other... Please describe:

What is the current behavior?

Issue Number: #2911

What is the new behavior?

This PR fixes the issues described in #2911 by upgrading the outdated apollo client to a much newer version. The issue was not caused by an upstream bug, but by outdated dev dependencies incomatible with current prod dependencies.

Comment on lines +39 to +44
onConnect: (
context: Context<
any,
{ socket: { close: (number, string) => any | boolean } }
>,
) => {
Copy link
Copy Markdown
Contributor Author

@erikwrede erikwrede Jul 11, 2023

Choose a reason for hiding this comment

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

Did this to fix the typescript errors, if anyone can point me towards the right type that is used here, I'm happy to adjust this line, IMO using any, just like upstream, here is sufficient for the tests though.

@erikwrede
Copy link
Copy Markdown
Contributor Author

@kamilmysliwiec any chance to get a review on this? 😊

@bel7aG
Copy link
Copy Markdown

bel7aG commented Oct 25, 2023

@erikwrede looks like a conflict that can block the release of this.

@erikwrede
Copy link
Copy Markdown
Contributor Author

erikwrede commented Oct 25, 2023

@bel7aG since this is a dependency upgrade the package lock is changing a lot.

If @kamilmysliwiec gives an okay I can update the lock immediately. Otherwise, there's little sense in updating the lock every week without feedback, given the frequent renovate dependency updates.

@kamilmysliwiec
Copy link
Copy Markdown
Member

#2704 (comment)

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