Post type setting field added

[jayedul]

Description of the Change

As per current implementation, there is no way to resolve the issue other than explicitly adding convert-to-blocks support during custom post type registration. So, a new field added in writing setting page to enable/disable Convert to Blocks for specific post types without editing code.

Closes #57

How to test the Change

• Register custom post type
• Edit/create post
• Toggle the post type in writing setting page under Convert to Blocks section
• Check if Gutenberg editor gets enabled/disabled for that post type correctly

Changelog Entry

Added - Setting field added to enable/disable specific custom post type

Credits

Props @jayedul

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added tests to cover my change.
• All new and existing tests pass.

[Sidsector9]

@jayedul I am seeing the following error in the Settings > Writing page, can you have a look at it?

[Sidsector9]

@jayedul let me know if I'm understanding this correctly. Should we limit the post types shown to only those that support the block editor? I don't think oEmbed responses, template parts, etc should be a part of this for the same reason.

If so, we can check the support using:

if ( ! use_block_editor_for_post_type( $post_type ) ) {
	continue;
}

Let me know what you think.

[jayedul]

@Sidsector9 I added the checking initially. Then removed as it doesn't exclude all the unnecessary types. You can see in the screenshot before and after adding the check.

[Sidsector9]

@jayedul So I checked, and it seems that template parts, oEmbed does have support for the block editor.
However, I think we can still use use_block_editor_for_post_type() to remove the ones which don't have support.

[jayedul]

@Sidsector9 Block editor check has been added. It can be re-reviewed though eslint test is failing here. There is no JS change in this PR, so I guess this issue is better to be fixed in a new ticket.

[Sidsector9]

@jayedul I am seeing fatal error when I save settings after unchecking all the checkboxes.

[jayedul]

in_array check issue is fixed now. Re-review requested though eslint check is failing. Eslint issue is coming from another package @10up/eslint-config.

[jeffpaul]

@Sidsector9 back to you for review