Skip to content
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

Notification Pattern #393

Closed
npathai opened this issue Mar 2, 2016 · 19 comments
Closed

Notification Pattern #393

npathai opened this issue Mar 2, 2016 · 19 comments
Assignees
Labels
epic: pattern status: stale issues and pull requests that have not had recent interaction type: feature

Comments

@npathai
Copy link
Contributor

npathai commented Mar 2, 2016

http://martinfowler.com/eaaDev/Notification.html

An object that collects together information about errors and other information in the domain layer and communicates it to the presentation.

@kuzneana
Copy link

Is this issue still free? Can I work on it?

@iluwatar
Copy link
Owner

Please go ahead @kuzneana

@iluwatar
Copy link
Owner

@kuzneana are you still working on this?

@iluwatar
Copy link
Owner

This issue is free for taking again.

@arjunduggal
Copy link

hi @iluwatar
Is this still open? If yes, can I take this up?
Thanks

@ohbus
Copy link
Contributor

ohbus commented Feb 11, 2021

@arjunduggal Thank you so much for your interest in taking this up! ⭐ Yes you can take this up!

🕐 Please keep us posted about when we can expect a Pull Request against this issue.
🤝 Looking forward to your contribution.
📖 Be sure to check out our Wiki section

@arjunduggal
Copy link

thanks @ohbus , I'm working on this one and will keep you posted on the update.

@ohbus
Copy link
Contributor

ohbus commented Jun 14, 2021

thanks @ohbus , I'm working on this one and will keep you posted on the update.

Hey @arjunduggal, any updates?

@iluwatar
Copy link
Owner

iluwatar commented Oct 9, 2021

This issue is free again

@NatalieSty
Copy link

@iluwatar I would like to work on this issue. Can you please assign it to me? Thanks!

@ohbus
Copy link
Contributor

ohbus commented Oct 19, 2021

@iluwatar I would like to work on this issue. Can you please assign it to me? Thanks!

⭐ Sure thing! Thanks for your interest in our project 😃

✔️ Please mention a 📆 timeline 🕙 for when can we expect 🤔 a Pull Request against this issue.

🤝 Looking forward to your contribution.
📖 Be sure to check out our Wiki section

@NatalieSty
Copy link

We expect to submit a pull request by start of December

@DateNolan
Copy link

@iluwatar Hey there, would I be able to work on this issue?

@Dehaoa
Copy link

Dehaoa commented Oct 7, 2022

@iluwatar Hi, Can I work on it?

@iluwatar
Copy link
Owner

iluwatar commented Oct 8, 2022

The fastest wins, so assigned to @DateNolan

@stale
Copy link

stale bot commented Nov 28, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@iluwatar
Copy link
Owner

iluwatar commented Dec 3, 2022

The issue is free again, if anyone else wants to try

@sugan0tech
Copy link
Contributor

@iluwatar can I also work on this?

Copy link

stale bot commented Dec 7, 2023

This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status: stale issues and pull requests that have not had recent interaction label Dec 7, 2023
@iluwatar iluwatar closed this as completed Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic: pattern status: stale issues and pull requests that have not had recent interaction type: feature
Projects
Archived in project
Development

No branches or pull requests

9 participants