Stub basic post type and API endpoint

[iandunn]

This creates a basic CPT, and tweaks Core's REST API endpoints to support listing and searching patterns.

Example API requests:

• Browse all: http://wporg-pattern.test/wp-json/wp/v2/wporg-pattern?_fields=title,content,meta,_links&_embed=wp:term
• Browse category: http://wporg-pattern.test/wp-json/wp/v2/wporg-pattern?_fields=title,content,meta,_links&_embed=wp:term&category=2
• Search: http://wporg-pattern.test/wp-json/wp/v2/search?search=head&subtype=wporg-pattern&_embed=self&_fields=_links

Fixes #4

[ryelle]

CPT looks good (once I locally fixed the console warning with the keys) 👍

Since this isn't using wp-scripts, it's not running the linter, and there are lint issues in the JS. You should be able to copy the pattern-creator package.json entirely, then add this project as a workspace here, and it'll automatically work. Well, the JS file will need to move to src, or you can pass --entry=./javascript/pattern-post-type.js to wp-scripts, it'll still build to /build. This can happen in this PR or a follow up.

[ryelle]

Since we're already setting up the workspaces with a shared wp-scripts build process, I think it would be a better dev-experience to have this use it - we can let the build step handle pulling out dependencies, and will save us from needing to remember that one place uses a different syntax than others.

[iandunn]

I can see the appeal of everything using the same tooling, but it still feels to me like this doesn't need any tooling, and that the devex is better without me.

The existing tooling might might it easier to set this up, but it could still be a pain. The biggest cost IMO is using the tooling, though. It's slow, it's breaks often and is painful to fix, etc.

This is already working, too, so I don't see any benefit from redoing it now. If we want to add more fields or components later, then I can see that making the plugin complex enough where JSX would be worth the costs.

[iandunn]

the console warning with the keys

What was that?

[iandunn]

Oh, you were getting that typical warnings about missing keys. Huh, that's weird that I didn't. Oh well 🤷🏻‍♂️

[iandunn]

I'm gonna merge this since I'm leaving on AFK soon, but feel free to open an issue about JSX, or just make the change if you feel strongly.