Volto view resolution order

[JeffersonBledsoe]

Currently we are using the following view resolution order:

• get view by layout
• get view by type
• get default view
  as defined in volto/packages/volto/src/components/theme/View/View.jsx at a923fab18b04664476198f9c88efcc760b443fd2 · plone/volto · GitHub.
  However, the effective Volto training suggests that the 'Content type' view should come first. I think this would be the desired behaviour, as 'A view for a content type' is really specific whilst layouts are a bit more generic. Was there a decision somewhere that I can't find related to this, or is this a bug (maybe breaking change?) which should be resolved?

As most content types have a default_view set, they come with a layout which makes it difficult to use the 'contentTypesViews' config as an escape hatch

[davisagli (David Glick)]

It was changed in This Enable us to change the default content type view by iRohitSingh · Pull Request #2625 · plone/volto · GitHub so that it's possible to give a content type configurable layouts, but also have a default view for the content type.

I'm not sure I see the problem. If you want to pick the view based on the layout property, register the layout name in config.views.layoutViews. If you don't want to, don't do that.

[JeffersonBledsoe]

The problem was that when default_view is set on a content type, the layout gets picked first so there's no opportunity to specify that a content type should use a particular view. I thought it was set for core Dexterity types, but this doesn't seem to be the case and was a custom content type thing actually so sorry for the noise