-
Notifications
You must be signed in to change notification settings - Fork 13.5k
feat(modal): add IonModalToken for injecting modal elements in Angular components #30474
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
base: feature-8.7
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to include tests for this? Or at the very least add it to a test page like angular/test/base/src/app/standalone/
and angular/test/base/src/app/lazy/
?
Other than that, no issues!
…eating and accessing modals through angular
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Shouldn't this go into |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great solution! My only feedback is a spelling issue in the tests.
Also my previous comment about changing the branch this targets to feature-8.7
since this is a feature. 👍
packages/angular/test/base/src/app/standalone/home-page/home-page.component.html
Outdated
Show resolved
Hide resolved
packages/angular/test/base/src/app/standalone/programatic-modal/modal/modal.component.html
Outdated
Show resolved
Hide resolved
...ages/angular/test/base/src/app/standalone/programatic-modal/programatic-modal.component.html
Outdated
Show resolved
Hide resolved
packages/angular/test/base/src/app/standalone/programatic-modal/programatic-modal.component.ts
Outdated
Show resolved
Hide resolved
packages/angular/test/base/src/app/standalone/programatic-modal/programatic-modal.component.ts
Outdated
Show resolved
Hide resolved
packages/angular/test/base/src/app/standalone/app-standalone/app.routes.ts
Outdated
Show resolved
Hide resolved
...ges/angular/test/apps/ng19/src/app/standalone/programatic-modal/programatic-modal.service.ts
Outdated
Show resolved
Hide resolved
...s/angular/test/apps/ng19/src/app/standalone/programatic-modal/programatic-modal.component.ts
Outdated
Show resolved
Hide resolved
...s/angular/test/apps/ng19/src/app/standalone/programatic-modal/programatic-modal.component.ts
Outdated
Show resolved
Hide resolved
...s/angular/test/apps/ng19/src/app/standalone/programatic-modal/programatic-modal.component.ts
Outdated
Show resolved
Hide resolved
Changed target branch and fixed the spelling of programmatic, thanks! |
Issue number: resolves #internal
What is the current behavior?
Currently, we provide no injection access to angular modals, which makes it difficult to connect to their events normally.
What is the new behavior?
This is an attempt to allow easier programmatic access to the internals of injected modals.
Does this introduce a breaking change?
Other information
Dev build:
8.6.2-dev.11749830167.1460aa73