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

Adopt the moveAssetsInOrder transform from core #2

Merged
merged 5 commits into from
Jul 5, 2020

Conversation

papandreou
Copy link
Member

Also, avoid relying on the query compilation by rewriting the queryObj to a predicate function. I think that's much easier to read.

This will allow us to get rid of the moveAssets and moveAssetsInOrder transforms in the next major version of assetgraph 😌

@Munter
Copy link
Member

Munter commented Jul 5, 2020

The switch from sift to pure javascript does indeed make it a lot easier to read.

Should we also pull in the tests for the new additions that are moving over? I don't know if the tests for the file hashing part cover enough to guarantee we can avoid regressions

@papandreou
Copy link
Member Author

I don’t think it’s necessary with more tests, it’s just some helper functions, really.

The switch from sift to pure javascript does indeed make it a lot easier to read.

Yeah, makes me wonder if the whole query syntax thing is even worth it. It was always a pretty hard thing to explain. I’m thinking about moving it to some kind of plugin, or maybe just ditching it.

@Munter
Copy link
Member

Munter commented Jul 5, 2020

If we ever wanted to supply typescript types for stuff in assetgraph it would certainly be easier to just let people write their own filtering function instead of attempting to make sift typed somehow

@Munter Munter merged commit a8cf089 into master Jul 5, 2020
@Munter Munter deleted the tech/adoptMoveAssetsInOrderTransform branch July 5, 2020 19:55
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

Successfully merging this pull request may close these issues.

2 participants