-
Notifications
You must be signed in to change notification settings - Fork 2
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
Extract computations notification types #620
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: AAJELLAL <[email protected]>
Signed-off-by: AAJELLAL <[email protected]>
… handle-params-notification
… handle-params-notification
Signed-off-by: AAJELLAL <[email protected]>
Signed-off-by: AAJELLAL <[email protected]>
… handle-params-notification
Signed-off-by: AAJELLAL <[email protected]>
Signed-off-by: AAJELLAL <[email protected]>
… handle-params-notification
Signed-off-by: AAJELLAL <[email protected]>
Signed-off-by: AAJELLAL <[email protected]>
…into handle-params-notification
Signed-off-by: Mathieu DEHARBE <[email protected]>
Quality Gate passedIssues Measures |
I think it's an anti pattern to have a constants class |
I don't think so : the anti-pattern described in your article is "A Large Global Constants Class" which contains everything. Here I have a "type" (ComputationsNotificationTypes) for the constant class. The NotificationService with its dozens of constants was much closer to the anti pattern in my opinion. Look a the good pattern he describes at the end : "4.2. Constants Class" If you prefer I can put them into ComputationType. But given that this is an enum and not a class I would have to add a nested class like this : |
removes a Circular dependency from #614