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.

Sign up for GitHub

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

Update next container API docs #331

Merged
merged 2 commits into from
Jan 20, 2025
+1 −3
Merged

Update next container API docs #331

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ff01820
feat(inversify-site): update docs
notaphplover Jan 20, 2025
1010007
fix(inversify-site): fix link address
notaphplover Jan 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...ify-site/blog/2025-01-20-announcing-inversify-7-0-0-alpha-0-prerelease/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ authors: [notaphplover]
tags: []
---

It's been a while since the last time `inversify` released a major version. Some exciting changes are on their way, and we are announcing them in a prerelease so you can participate and [discuss](https://github.com/inversify/monorepo/discussions/235) them before it's finally released.
It's been a while since the last time `inversify` released a major version. Some exciting changes are on their way, and we are announcing them in a prerelease so you can participate and [discuss](https://github.com/inversify/InversifyJS/discussions/1712) them before it's finally released.

<!-- truncate -->

Expand Down
2 changes: 0 additions & 2 deletions packages/docs/services/inversify-site/docs/api/container.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,6 @@ You can query the configuration and resolve configured dependencies with the `ge
You can react to resolutions with container activation handlers and unbinding with container deactivation handlers.
You can create container hierarchies where container ascendants can supply the dependencies for descendants.
For testing, state can be saved as a snapshot on a stack and later restored.
For advanced control, you can apply middleware to intercept the resolution request and the resolved dependency.
You can even provide your own annotation solution.

## Container Options

Expand Down
Loading