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

GLSP-1449: Ensure that codebase is compatible with inversify >= 6.1.3 #407

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

tortmayr
Copy link
Contributor

What it does

  • Remove usage of not-exported constant in lazy injector
  • Fix constructor injection of classes that are overwritten to replace constructor injection with lazy injection. To pass the stricter type checks of newer inversify version we need to inject an empty array here.

This ensures that the code base is compatible with all 6.x versions of inversify and we can hard pin/resolve the version required for newer Theia versions while other integrations don't require any change.

Part of eclipse-glsp/glsp#1449

How to test

Add a resolutions block in the root package. json

"resolutions": { "**/inversify":"^6.1.3"}

Build and start the application. Everything should still work as expected.

Follow-ups

Changelog

  • This PR should be mentioned in the changelog
  • This PR introduces a breaking change (if yes, provide more details below for the changelog and the migration guide)

- Remove usage of not-exported constant in lazy injector
- Fix constructor injection of classes that are overwritten to replace constructor injection with lazy injection. To pass the stricter type checks of newer inversify version we need to inject an empty array here.
Copy link
Contributor

@martin-fleck-at martin-fleck-at left a comment

Choose a reason for hiding this comment

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

LGTM!

@tortmayr tortmayr merged commit a980896 into master Dec 16, 2024
7 checks passed
@tortmayr tortmayr deleted the glsp-1449 branch January 14, 2025 16:32
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