New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce the idea of views in the builder #269
Comments
seancdavis
added a commit
that referenced
this issue
Jun 25, 2018
seancdavis
added a commit
that referenced
this issue
Jun 25, 2018
seancdavis
added a commit
that referenced
this issue
Jun 25, 2018
seancdavis
added a commit
that referenced
this issue
Jun 25, 2018
Rendering shares the elements#search view
seancdavis
added a commit
that referenced
this issue
Jun 25, 2018
seancdavis
added a commit
that referenced
this issue
Jun 25, 2018
seancdavis
added a commit
that referenced
this issue
Jun 25, 2018
seancdavis
added a commit
that referenced
this issue
Jun 25, 2018
seancdavis
added a commit
that referenced
this issue
Jun 25, 2018
seancdavis
added a commit
that referenced
this issue
Jun 28, 2018
seancdavis
added a commit
that referenced
this issue
Jun 28, 2018
seancdavis
added a commit
that referenced
this issue
Jun 28, 2018
seancdavis
added a commit
that referenced
this issue
Jun 28, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These are specific queries/subsets of elements that can be saved to the property. That is what drives the left-side navigation of the property.
Out of the box there should be an Recent view (all, reverse ordered by
updated_at
) and a view for each (non-hidden) template.This will make it much easier to transition to templates and fields being in the database.
The text was updated successfully, but these errors were encountered: