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
Hi, thanks for a great plugin, love the automatic tag based filters!
So much so that I was wondering if it is possible to make a custom input or pass a filter to the custom asset source to only show / allow files with a certain tag.
(Ideally it wouldn't accept file uploads either).
If it's not possible atm, consider it a feature request and if so I can go into more detail about the use cases
The text was updated successfully, but these errors were encountered:
However for the native image input I don't think that's possible right now. Looking at the source there is no information about the field being passed along to the plugin. There is the document though, and theoretically we could parse the schema and find out any other properties like filters on the fields. However this fails pretty quickly when you have multiple image fields defined in your schema. So that's not a viable option.
I don't think you'd really want to build a custom image component, do you?
I'll see if I can file an issue or a PR with Sanity to ask if it's possible to get any schema info available inside the plugin.
I agree that a custom image component would be a bad idea unless it could retain everything else around the "native" image component, which is unlikely.
If PR / Feature request to sanity then maybe this should be split into two parts:
Option do disable upload and use selection only on image inputs
Ability to pass along options from image input into custom asset source
Hi, thanks for a great plugin, love the automatic tag based filters!
So much so that I was wondering if it is possible to make a custom input or pass a filter to the custom asset source to only show / allow files with a certain tag.
(Ideally it wouldn't accept file uploads either).
If it's not possible atm, consider it a feature request and if so I can go into more detail about the use cases
The text was updated successfully, but these errors were encountered: