add: usage examples in core editor docs

[troychaplin]

What?

Usage examples in documentation for core/editor package for editPost, getEditedPostAttribute and getCurrentPostType. Part of #42125

Why?

Because examples are important and help devs learn to use the tools

How?

The noted selectors / actions had no examples prior to this PR

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: troychaplin <areziaal@git.wordpress.org>
Co-authored-by: ryanwelcher <welcher@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[ryanwelcher]

Try running npm run lint:js:fix to see if that updates the examples to match the standards.

[ryanwelcher]

Suggested change

	const currentPostType = wp.data.select('core/editor').getCurrentPostType()
	const currentPostType = wp.data.select( 'core/editor' ).getCurrentPostType()

[ryanwelcher]

Looks like the whitespace is different than WP coding standards and that's what is failing .

[troychaplin]

I got my formatting conflict fix up in vscode, and it appears to be using WP standards (it's been a min, been uring psr for a long time) but it's still failing. If I try and run npm run lint:js:fix I get a warning that stops the process, which also happens to me when I update trunk. This might be a new issue? I'll have to check the issues

[ryanwelcher]

I just took a quick look and there seems to be a lot of whitespace changes that don't look like they should be there.

[troychaplin]

I just took a quick look and there seems to be a lot of whitespace changes that don't look like they should be there.

A bit confused on this one. I can't run npm run lint:js:fix due to a conflict with@typescript-eslint/typescript-estree. I downgraded typescript to version 5.1.6, which allows the lint fix to run, and while there's a lot of warnings, nothing shows as being changed other than my expected package files.

[ryanwelcher]

LGTM!

[flexseth]

🙌