Remove standard node types from project definitions #56615

New Issue

Sybren A. Stüvel · 2018-08-30T14:22:26+02:00

Sybren A. Stüvel commented

2018-08-30 14:22:26 +02:00

Upgrading node type definitions is now a huge hassle, as each project (including the ca 8000 home projects we have now) have their own copy of this identical data. Furthermore, the structure of the node types tends to be tightly coupled with the implementation (for example the attachments schema).

My suggestion is to remove all node types from projects, and replace them with a list of node type names that have been activated for the project.

Upgrading node type definitions is now a huge hassle, as each project (including the ca 8000 home projects we have now) have their own copy of this identical data. Furthermore, the structure of the node types tends to be tightly coupled with the implementation (for example the attachments schema). My suggestion is to remove all node types from projects, and replace them with a list of node type names that have been activated for the project.

Sybren A. Stüvel commented

2018-08-30 14:22:26 +02:00

Added subscribers: @dr.sybren, @fsiddi

Francesco Siddi commented

2018-09-03 20:52:09 +02:00

Sounds good. We should discuss how to handle node_type properties overrides (for example predefined values, or allowed values).
Probably this makes "migrations" easier, and reduces complexity when validating nodes so it's really exciting!

Sounds good. We should discuss how to handle node_type properties overrides (for example predefined values, or allowed values). Probably this makes "migrations" easier, and reduces complexity when validating nodes so it's really exciting!

Sign in to join this conversation.