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

Allow complex conditions #210

Open
wuuti opened this issue Dec 15, 2016 · 1 comment
Open

Allow complex conditions #210

wuuti opened this issue Dec 15, 2016 · 1 comment

Comments

@wuuti
Copy link
Contributor

wuuti commented Dec 15, 2016

Summary

It currently seems impossible to finegrain what gitify exports in a partition. (only a "where" on the objects data fields is possible). This is especially useful if you have a large installation where you don't want to integrate everything in your git workflow, but e.g. contexts you are currently developing on.

Step to reproduce

Try, for example, to export only moreGallery data from a certain context. While it is easy to export resources from a context:

where:
      -
        'context_key:IN': [web,exportme]

that is not possible for moregallery images, as these are stored only in relation to the resource they are in. The context_key is (correct for normalized dbs) not stored along with the resource keys in moregallery_image, and so not usable in our where condition on the images.

Expected behavior

So we would need something like

where:
      -
        '<lookup resource>.context_key:IN': [web,exportme]

or the possibility to define a join to get the data for the conditional.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@Mark-H
Copy link
Member

Mark-H commented Dec 15, 2016

I think joins and complex filters like that are getting kinda out of scope... at the very least you're making your development and workflow very complex too, while it might be better to keep it simple.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants