-
Notifications
You must be signed in to change notification settings - Fork 14
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
Ticket #1996: Add documentation on models affected by signals #2151
Ticket #1996: Add documentation on models affected by signals #2151
Conversation
🥳 Successfully deployed to developer sandbox za. |
…ttps://github.com/cisagov/manage.get.gov into za/1996-add-documentation-on-models-affected-by-signals
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
1 similar comment
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
🥳 Successfully deployed to developer sandbox za. |
docs/developer/README.md
Outdated
2. Where possible, avoid chaining signals together (i.e. a signal that calls a signal). If this has to be done, clearly document the flow. | ||
3. Minimize logic complexity within the signal as much as possible. | ||
4. Don't use signals when you can use another method, such as an override of `save()` or `__init__`. |
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 would move this to number one
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 callout
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.
Approve but maybe wait on one more person to read really fast to make sure it makes sense to more devs as we want this to be readable and usable by future developers. @dave-kennedy-ecs I think it was you and Rachid once had a heck of time trouble shooting signals, maybe you would be a good candidate to at least give the readme file a quick look.
🥳 Successfully deployed to developer sandbox za. |
1 similar comment
🥳 Successfully deployed to developer sandbox za. |
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.
From a person-who-hasn't-used-signals perspective, this documentation is really clear of how/where/why we're using it - LGTM!
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.
Documentation is clear and comprehensive.
Ticket
Resolves #1996
Changes
Context for reviewers
In an eng huddle, we concluded that we should be more thorough in regards to our signals as they are often hard to debug. This PR adds some documentation as well as overarching guidelines which new and old developers can use when approaching them.