Skip to content
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

Streamline the selection of elements to be loaded into models #32

Closed
petrsvihlik opened this issue Sep 4, 2017 · 1 comment
Closed
Labels
blocked enhancement groomed The issue has been groomed and should be in a good shape. help wanted

Comments

@petrsvihlik
Copy link
Contributor

petrsvihlik commented Sep 4, 2017

Blocked by: #35

Motivation

Currently, the developer needs to name elements that should be loaded from KC. If the data is used at multiple places, it's hard to keep track of what needs to be included in the model at which place.
We'd like to come up with a way of defining elements that are necessary to successfully render a view.

Design guidelines

An idea was to use the (view)models as the source of truth.

There should be a way to construct ElementsParameter just by providing a viewmodel.

@JanLenoch JanLenoch changed the title Enforce elements are loaded in models Streamline the selection of elements to be loaded into models Sep 11, 2018
@JanLenoch JanLenoch added the groomed The issue has been groomed and should be in a good shape. label Sep 11, 2018
@petrsvihlik
Copy link
Contributor Author

doesn't make much sense now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked enhancement groomed The issue has been groomed and should be in a good shape. help wanted
Projects
None yet
Development

No branches or pull requests

2 participants