Skip to content
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.

Allow components to be stored in sub-collections #17

Closed
2 tasks
brettwillis opened this issue Jul 20, 2020 · 1 comment
Closed
2 tasks

Allow components to be stored in sub-collections #17

brettwillis opened this issue Jul 20, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@brettwillis
Copy link
Member

Currently, components (repeatable) and dynamic zone are stored directly in the document. This does not provide good support for running queries on fields within those components.

  • Add an option flattenComponents (global setting and per-model override) wich defaults to true current behaviour.
  • On the per-model option, allow to specify a test for selecting which components are flattened.

When component flattening is disabled, store the components as individual documents within a sub-collection of the master document.

@brettwillis brettwillis added the enhancement New feature or request label Jul 20, 2020
@brettwillis brettwillis self-assigned this Jul 20, 2020
@brettwillis
Copy link
Member Author

I have added indexing of repeatable and dynamic zone components, so querying is no supported (in a limited, preconfigured way).

I feel that the benefits currently outweigh the downsides of embedded components, so I'll close this enhancement for now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant