Add Additional Webspaces Field to Settings Tab

[alexander-schranz]

Most entities like Article and any routable Custom Entity will have a webspace selection in its settings tab. I did go here with the name WebspaceInterface.

The entity like Page will not implement it as the webspace will there not be on the PageDimensionContent Entity and so not implement for its webspace a content interface. Other entity like snippet which will have content will not have a Webspace field or relation.

TODO

• Discuss how additionalWebspaces are saved
  • Version A: JSON Field (performant smart content query)
  • Version B: Additional Table with Webspace (primaryKey is webspaceKey)
  • Version C: Additional General Table (DimensionContentWebspace entity)
  • Version D: Additional Table without ORM (not sure if possible)

See prototype repository: alexander-schranz/doctrine-json-array-prototype#1

Keep in mind for navigationContexts we need something similar, but as they are Page specific and will not be part of the content bundle it is not as important as additionalWebspaces which will be used by any entity using content bundle with routing.

[coveralls]

Pull Request Test Coverage Report for Build 1343203423

• 49 of 49 (100.0%) changed or added relevant lines in 5 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 1340881271:	0.0%
Covered Lines:	2058
Relevant Lines:	2058

---

💛 - Coveralls

[alexander-schranz]

As discussed with @chirimoya we will go with a one-to-many relation.

The content bundle will provide also a AdditionalWebspaceTrait content bundle so a article bundle for example has then 3 entities:

Article
ArticleDimensionContent
ArticleDimensionContentWebspace

The ArticleDimensionContentWebspace will have id, dimensionContent and webspace field.

/cc @TheCadien do you want to have a look at this?

[TheCadien]

@alexander-schranz i do that