Skip to content

Add PR review norms for the mobile team#23

Open
shubham1g5 wants to merge 2 commits intomasterfrom
review_norms_mobile
Open

Add PR review norms for the mobile team#23
shubham1g5 wants to merge 2 commits intomasterfrom
review_norms_mobile

Conversation

@shubham1g5
Copy link
Copy Markdown
Contributor

Summary

Adds PR review norms for mobile PR reviews based on a team session

Changeset Category

This PR is streamlined for review in the following category

  • Modernization
  • Bug Fix
  • Process
  • Refactor
  • Performance
  • Documentation

shubham1g5 added 2 commits May 8, 2026 12:35
Added a reference to PR review norms in the mobile standards document.
@shubham1g5 shubham1g5 marked this pull request as ready for review May 8, 2026 07:13
Copy link
Copy Markdown
Contributor

@conroy-ricketts conroy-ricketts left a comment

Choose a reason for hiding this comment

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

Looks great! I just had one minor comment

- **Repeated or inline logic** — copy-pasted blocks or complex lambdas that deserve a named method
- **Duplicate utilities** — if something already exists in the codebase, point it out
- **Null safety (`!!`)** — we use the fail-fast approach; removing `!!` without discussion should be flagged
- **TODO hygiene** — every TODO needs either a Jira ticket reference or a sentence explaining the deferral
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Think these norms should be developer-agnostic (i.e. they should 100% apply to open source developers as well). Can we remove the mention of Jira tickets here in favor of just "a sentence explaining the deferral"?

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.

2 participants