Heads up that there's some sort of recently-ish introduced conflict between Toolset Views and FSE theme (TwentyTwentyTwo in this case). When Toolset Views plugin is enabled, the message "The editor has encountered an unexpected error." is shown on /wp-admin/site-editor.php. I wish I could say at what version this started happening.
The solution at the moment is to disable Views plugin, make site edit changes, then re-enable plugin.
I'm not sure what's causing the problem you are seeing. I just tried using the Theme editor for 2022 theme on my local test site that has the latest version of Toolset Blocks and other Toolset plugins installed, and it didn't trigger any such errors, even when designing a page that included a View block.
That's interesting. So maybe it's just us, or TwentyTwentyTwo. But I would also like to note that it was the old school Views plugin, not Blocks, that was causing the conflict. Some of us still prefer code view (plus the greater options), despite using FSE on new sites in an attempt to somewhat keep pace with the way the WP wind blows. I understand you can't use specific features of Toolset, like archive templates, with FSE but I didn't realize everything-Toolset was unsupported with FSE.
For what it's worth, I've had success using Toolset content templates more like snippets that I can insert into the FSE post templates to show Toolset custom fields, or even WP fields the way we want. It may make a difference that I'm still using the older code-view when creating my content templates and views? For example, we use the image caption field to capture & display the image's licensing/credits, but WP's feature image block doesn't include this, so I use a Toolset content template block to show this information. An example of a more complicated custom post type FSE template using Toolset custom posts, relationships, custom fields, content templates and views under the hood would be a page like hidden link. In my opinion you can still get the primary advantages of Toolset's features as long as you're willing to put up with creating the page/post templates in the FSE block editor. I do sorely miss Toolset's archive templates, however; I've resorted to pages with views for getting the customizations I want for those.
Anyway, I guess this plugin conflict is just something to watch for as you eventually delve into Toolset + FSE, whenever that will be. Thanks!
