-
Notifications
You must be signed in to change notification settings - Fork 1
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: add toastr service #23
base: main
Are you sure you want to change the base?
Conversation
WalkthroughThe update introduces enhancements to the Angular project by integrating the Toastr notification library, adding its CSS to the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
package-lock.json
is excluded by!**/package-lock.json
Files selected for processing (4)
- angular.json (3 hunks)
- package.json (3 hunks)
- src/app/shared/services/toastr.service.ts (1 hunks)
- tsconfig.json (1 hunks)
Additional comments not posted (11)
tsconfig.json (1)
9-9
: LGTM!The addition of
"allowSyntheticDefaultImports": true
is a good enhancement for compatibility with various JavaScript modules and libraries.The code changes are approved.
src/app/shared/services/toastr.service.ts (5)
9-17
: LGTM!The constructor correctly initializes the toastr options. Consider adding comments to explain the configuration options if needed.
The code changes are approved.
19-21
: LGTM!The
success
method correctly displays a success message using toastr.The code changes are approved.
23-25
: LGTM!The
error
method correctly displays an error message using toastr.The code changes are approved.
27-29
: LGTM!The
info
method correctly displays an info message using toastr.The code changes are approved.
31-33
: LGTM!The
warning
method correctly displays a warning message using toastr.The code changes are approved.
package.json (2)
34-34
: LGTM!The addition of
toastr
as a dependency is appropriate for the toastr service.The code changes are approved.
49-49
: LGTM!The addition of
@types/toastr
as a dependency is appropriate for TypeScript type definitions.The code changes are approved.
angular.json (3)
30-30
: LGTM!The addition of the Toastr CSS file to the styles array is appropriate and necessary for styling the Toastr notifications.
The code changes are approved.
90-90
: LGTM!The addition of the Toastr CSS file to the styles array in the test options is appropriate and necessary for styling the Toastr notifications during testing.
The code changes are approved.
106-107
: LGTM!The addition of the
analytics
property with a unique identifier in the CLI settings is appropriate for tracking and analytics purposes.The code changes are approved.
package.json
Outdated
@@ -31,6 +31,7 @@ | |||
"primeicons": "^6.0.1", | |||
"primeng": "^16.7.2", | |||
"rxjs": "~7.8.0", | |||
"toastr": "^2.1.4", |
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.
Any reason why we are using this?
We have created this foundation using primeNG. So we should be using toast from primeNG too?
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.
i took the toastr service from pickleball initial setup as suggested by Raj, there we were using toastr, also I don't see any primeng module imported in foundation right now, should I go ahead an add primeng.module.ts and use primeng toastr instead of this?
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.
Yes use primeng toastrs only. For Foundation we will rely on PrimeNG only
https://primeng.org/toast
package.json
Outdated
@@ -31,6 +31,7 @@ | |||
"primeicons": "^6.0.1", | |||
"primeng": "^16.7.2", | |||
"rxjs": "~7.8.0", | |||
"toastr": "^2.1.4", |
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.
Yes use primeng toastrs only. For Foundation we will rely on PrimeNG only
https://primeng.org/toast
Changes in PR:
Summary by CodeRabbit
New Features
ToastrService
for easy integration of notifications throughout the application.Enhancements
Dependencies
toastr
and its type definitions for notification support.