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

Ticket #1996: Add documentation on models affected by signals #2151

Merged

Conversation

zandercymatics
Copy link
Contributor

@zandercymatics zandercymatics commented May 8, 2024

Ticket

Resolves #1996

Changes

  • Adds documentation in the readme and on the contact/user object going over how, when, and why to use signals

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.

Copy link

github-actions bot commented May 8, 2024

🥳 Successfully deployed to developer sandbox za.

Copy link

github-actions bot commented May 8, 2024

🥳 Successfully deployed to developer sandbox za.

Copy link

github-actions bot commented May 8, 2024

🥳 Successfully deployed to developer sandbox za.

1 similar comment
Copy link

github-actions bot commented May 8, 2024

🥳 Successfully deployed to developer sandbox za.

Copy link

github-actions bot commented May 8, 2024

🥳 Successfully deployed to developer sandbox za.

Copy link

github-actions bot commented May 8, 2024

🥳 Successfully deployed to developer sandbox za.

@zandercymatics zandercymatics changed the title (Draft) Ticket #1996: Add documentation on models affected by signals Ticket #1996: Add documentation on models affected by signals May 8, 2024
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__`.
Copy link
Contributor

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great callout

Copy link
Contributor

@abroddrick abroddrick left a 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.

Copy link

github-actions bot commented May 8, 2024

🥳 Successfully deployed to developer sandbox za.

1 similar comment
Copy link

github-actions bot commented May 8, 2024

🥳 Successfully deployed to developer sandbox za.

Copy link
Contributor

@therealslimhsiehdy therealslimhsiehdy left a 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!

Copy link
Contributor

@dave-kennedy-ecs dave-kennedy-ecs left a 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.

@zandercymatics zandercymatics merged commit 6d0220e into main May 13, 2024
10 checks passed
@zandercymatics zandercymatics deleted the za/add-documentation-on-models-affected-by-signals branch May 13, 2024 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add documentation on models affecting or being affected by signals
4 participants