You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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:
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
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.
The text was updated successfully, but these errors were encountered: