[wp-meta] [Making WordPress.org] #5303: Block plugin validation tool UI improvements

[Making WordPress.org]

#5303: Block plugin validation tool UI improvements
------------------------------+---------------------
 Reporter:  tellyworth        |       Owner:  (none)
     Type:  task              |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by ryelle):

 [attachment:"collapsible-details-plugin.diff"] & [attachment:"collapsible-
 details-theme.diff"] switch away from the external help page, and add
 inline expandable help text to each check type. I think this gives a
 better dev experience, and will be translatable. The downside is needing a
 code change to update docs, but it seems that's how the other pages work.

 There are still todo notes & other questions in this patch, but it's a
 first pass at adding descriptions to each check. I also collapsed all the
 `check_block_json_is_valid` issues into one section, since it can get
 wordy :)

 Speaking of `check_block_json_is_valid`, I think it's a little aggressive
 — my test block uses script handles for editorScript, and it's flagging
 every one of them since they don't end in `.js`. Is that a requirement for
 finding the assets in the API?

 I also had the idea to make a check for a well-formed block name— it
 should be alphanumeric, start with a letter, and contain one slash for
 namespace. If we
 [https://github.com/WordPress/gutenberg/pull/23545#discussion_r449391695
 agree that this should be the plugin slug,] it could also check that.
 Otherwise a basic check that it isn't one of `[ cbg, example, block, core
 ]` seems good to me (other example prefixes I should add?).

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5303#comment:16>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org