[Type] Developer Documentation - Fix removeAllNotices dispatch on the removeAllNotices doc section of @wordpress/notices

[leomuniz]

What?

This PR replaces the missed removeNotices from useDispatch( noticesStore )with the removeAllNotices on the removeAllNotices section of the Gutenberg Reference Guide of the @wordpress/notices package.

Why?

The Usage example of the removeAllNotices section has a bug that prevents the code from working properly. It dispatches the removeNotices from noticesStore but it tries to use the removeAllNotices() method when clicking on the buttons below.

It seems that this removeAllNotices section was copied from the removeNotices section, but it missed replacing all the occurrences of the removeNotices method.

How?

It just replaces the removeNotices with removeAllNotices on the removeAllNotices doc section.

Testing Instructions

Not relevant as it doesn't change any working code.
But if you want to test the provided example, you must copy the code and paste it into a new React component, then, import it to be used in a React page (e.g. a WordPress admin page).

Testing Instructions for Keyboard

Not relevant

Screenshots or screencast

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @leomuniz! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[t-hamano]

Thanks for the PR!

I think this change is correct, but the content of this markdown file is auto-generated from SDoc. Therefore, you need to change the following parts:

gutenberg/packages/notices/src/store/actions.js

Line 331 in 83e1a2c

* select( noticesStore ).getNotices()

Then run npm run docs:build. That way GitHub Actions will also pass.

[leomuniz]

Thank you, @t-hamano

I didn't know this doc was auto-generated. I work on this change (I'll need to setup Gutenberg locally to do it) and update the issue asap.

Happy new year :)

[leomuniz]

Hey, @t-hamano

I made the change and ran the docs:build script. As expected, it generated the same doc file content I had manually changed previously. Then, I pushed the changes to this branch. But it was not enough to make all the Github actions pass.

I've debugged these errors a little bit and they don't seem related to the change I've made. Even the JS unit tests failing are actually failing in other parts of the code. So I'm not sure how to proceed.

Do you have any suggestions?
Thank you

[t-hamano]

LGTM!

I've debugged these errors a little bit and they don't seem related to the change I've made.

That's right, some GitHub Actions sometimes fail. All re-run GitHub Actions are ✅, so I would like to merge this PR.

Thank you for your contribution!