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

chore(docs): Rename ControllerMessenger to Messenger #5089

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Gudahtt
Copy link
Member

@Gudahtt Gudahtt commented Dec 20, 2024

Explanation

Rename ControllerMessenger to Messenger in the controller docs and examples.

References

Relates to #4538

Changelog

N/A

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've highlighted breaking changes using the "BREAKING" category above as appropriate
  • I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

Rename `ControllerMessenger` to `Messenger` in the controller docs.

Relates to #4538
@Gudahtt Gudahtt marked this pull request as ready for review December 20, 2024 06:04
@@ -121,7 +121,7 @@ type AllowedEvents = never;
* The messenger which is restricted to actions and events accessed by
* {@link GasPricesController}.
*/
export type GasPricesControllerMessenger = RestrictedControllerMessenger<
export type GasPricesMessenger = RestrictedMessenger<
Copy link
Contributor

@mcmire mcmire Jan 8, 2025

Choose a reason for hiding this comment

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

Hmm, should we still call controller messengers <Name>ControllerMessenger? I know it is a mouthful to say, but it aligns with how we are naming other controller types (GasPricesControllerState, GasPricesControllerActions, etc.) (I guess we could call service messengers <Name>ServiceMessenger as well, provided that the service class itself is called <Name>Service?)

Copy link
Member Author

Choose a reason for hiding this comment

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

Good question. We have examples of both conventions (e.g. NetworkState, PreferencesState).

I can update this to leave the names as they were before for now at least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants