-
Notifications
You must be signed in to change notification settings - Fork 117
Toast, Message, Modal fix for ix-angular/standalone, ix-react, ix-vue #2267
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: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 997d061 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
/gemini review |
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.
Code Review
This pull request introduces fixes for Toast, Message, and Modal components across Angular, React, and Vue packages, primarily by ensuring web components are defined before use. The changes look good and address the described issues. I've added a few comments with suggestions to improve maintainability and type safety by reducing code duplication and using stricter types. Specifically, I've pointed out areas in the Angular services where boilerplate can be reduced and consistency can be improved.
packages/angular/common/src/providers/message/message.service.ts
Outdated
Show resolved
Hide resolved
|


💡 What is the current behavior?
Some functions related to toast, message and modal need to be adjusted to call the relevant defineCustomElement().
GitHub Issue Number: #2263, #2060
🆕 What is the new behavior?
🏁 Checklist
A pull request can only be merged if all of these conditions are met (where applicable):
pnpm test)pnpm lint)pnpm build, changes pushed)