-
Notifications
You must be signed in to change notification settings - Fork 47
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
Is the "Current Entry" option coming back? #26
Comments
And, I'd be happy to make a PR that does this! I'm thinking it would be more performant to traverse the |
Hey @good-idea – in all honesty, this is something that just got accidentally left behind when switching to search facets!
That makes way more sense then what
There's no getting around another query though, but recursively grabbing those image asset refs (from the provided |
Fantastic, thank you! |
In It should be much faster now, as it's just recursively pulling those refs from the current document as suggested (rather than querying every single image, which was pretty mad in hindsight) Let me know if that doesn't work out for you! |
Love it, thank you! |
@robinpyon I'm working with an |
Hey @fabien – I wouldn't have thought that'd make a difference since the plugin is only concerned with underlying In any case, do you mind creating a new issue and pasting your schema? I'd be happy to look into this for you |
The ability to select from images that are only associated with the current document is really helpful - especially for one of my clients with a massive dataset with thousands of images. Will this be re-implemented in
1.x
?For now, I've reverted to
0.4.0
because this feature is crucial for them.The text was updated successfully, but these errors were encountered: