Closed dnsl48 closed 10 months ago
I've got a few more ;)
Sounds good. On the graphQL bit, it's worth pointing out that DBFile currently has it's own special grahpql type. https://github.com/silverstripe/silverstripe-graphql/blob/3/_config/assets.yml
We'll probably need some similar logic for this, but that's probably a problem for another card.
Just to clarify: With "Supports 10 link fields" I mean 10 entries in static $db
. We'll build in 4 link types (internal page, external URL, email, file), and a handful of projects might have one or two additional ones (e.g. phone number, document management system integration, etc). It's very unlikely that any Silverstripe project will have 10 link types.
Summary
In support for the RFC-30 we need to come up with a robust default AnyLink implementation.
That link type is expected to be used the most and should be able to represent other link types (depending on the CMS user choice).
Acceptance Criteria
RFC-30 Option C
data model description (DBComposite
)