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: backport resolve #228

Merged
merged 11 commits into from
Aug 10, 2024
Merged

feat: backport resolve #228

merged 11 commits into from
Aug 10, 2024

Conversation

bigopon
Copy link
Member

@bigopon bigopon commented Aug 10, 2024

As per the request at #227, a backport of resolve is provided in this PR.

This should help applications prepare for v2 migration, or if they like, stay with v1 without having to worry about Typescript.

  • improve container.get() typings so that .get(NewInstance.of())/Lazy/Factory etc... will give correct type inference.
  • fix the typings of @lazy/@newInstace as the existing typings are incorrect, the type of the keys are used to validate the target class of the decorator

Thanks @m-gallesio for requesting this.

Closes #227

cc @thomas-darling for your awareness since you are with one of the big v1 applications that I'm aware of.

@bigopon bigopon merged commit ccac164 into master Aug 10, 2024
2 checks passed
@bigopon bigopon deleted the feat/backport-resolve branch August 10, 2024 14:02
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.

Backport resolve from Aurelia 2
1 participant