Version Packages#24
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
0c96c59 to
ec171c6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
vitest-browser-angular@0.4.0
Minor Changes
✨ Add support for Angular 21 (by @gabrielmethot in #23)
✨ add input binding to withRouting with option to disable (by @shairez in #25)
By default, routing tests use Angular's
withComponentInputBinding(), which binds route params, query params, and routedatato matching component inputs.You can now pass
disableInputBinding: truein your routing config to turn this off. When disabled, the router is provided withoutwithComponentInputBinding(), so components won't auto-receive route data as inputs.Patch Changes
🐞🩹 routed component is now the activated route (by @shairez in #25)
When using
withRouting, the render result now correctly exposes the activated route's component ascomponentClassInstance(and uses the harness fixture for the same component).Previously,
componentClassInstanceandfixturecould refer to a different component than the one actually rendered for the current route. Now they match the component instance that Angular Router activated for the initial (or current) route, so assertions oncomponentClassInstance(e.g. route params likeuserId) and direct fixture access behave as expected in tests.