Skip to content

Conversation

@Cramsden
Copy link
Contributor

📜 Tickets

Jira ticket

💡 Description

Make StateType protocol equatable and all descending States equatable

🎥 Demos

Before After
Demo

📝 Checklist

  • I filled in the ticket numbers and a description of my work
  • I updated the PR name to follow our PR naming guidelines
  • I ensured unit tests pass and wrote tests for new code
  • If working on UI, I checked and implemented accessibility (Dynamic Text and VoiceOver)
  • If adding telemetry, I read the data stewardship requirements and will request a data review
  • If adding or modifying strings, I read the guidelines and will request a string review from l10n
  • If needed, I updated documentation and added comments to complex code

@Cramsden Cramsden requested a review from a team as a code owner December 12, 2025 19:32
@mattreaganmozilla
Copy link
Collaborator

🚀

@mobiletest-ci-bot
Copy link

mobiletest-ci-bot commented Dec 12, 2025

Messages
📖 Project coverage: 38.51%

🧹 Tidy commit

Just 3 file(s) touched. Thanks for keeping it clean and review-friendly!

🙌 Friday high-five

Thanks for pushing us across the finish line this week! 🙌

✅ Per-file coverage

All changed files meet the threshold of 35.0%.

Client.app: Coverage: 37.12

File Coverage
ActiveScreenState.swift 94.48%

Redux: Coverage: 92.26

File Coverage
Subscription.swift 100.0%

Generated by 🚫 Danger Swift against 0ede11b

Comment on lines +58 to +61
// State was updated but observers are not notified if the state is the same
guard newState != oldState else {
return
}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mattreaganmozilla I was thinking it could be good to have a log here at least in the beginning for debugging purposes but I am not sure if it is overkill or going to be weird to pass the logger to this level.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Honestly I think that would create too much spam in the console. 🤔 I had worked on a logger throttler for de-dup'ing messages a while back but never merged it (pretty sure this is the PR: #22547).

We could consider rolling that back in perhaps, it would probably help in scenarios like this.

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.

4 participants