Yeah, I didn't see any documentation on it yet, definitely would be good to
have. At least there is this thread for the moment. Thanks for the tip
about the setting.
Adam
On Mon, Mar 16, 2020 at 3:23 PM Alexei Peters wrote:
> I believe that you should be able to put the components anywhere.
I believe that you should be able to put the components anywhere. There's
a setting for that. "SEARCH_COMPONENT_LOCATIONS"
Which reminds me, that we need to document this feature.
Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
On Mon, Mar 16, 2020 at 12:40 PM Adam
Hi Alexei, thanks for the response on this, I think it's all the info I
need to get started in earnest. Can I place the filter anywhere in my
project and then register it from there? That would be great, as I (think)
it would mean that I would only have to migrate the core Arches js file
that
Hi Adam,
Everything you laid out is correct. I"m sure you've already done this, but
looking at the existing components should be enlightening.
Because you have no UI, then your client side code should be pretty
simple. All you should need to do is append your search parameter onto the
search url
Hi Brendon,
I think that you could satisfy this with a custom card component. I don't
think new data type is what you're looking for.
see
https://arches.readthedocs.io/en/stable/functions-widgets-datatypes/#card-components
Cheers,
Alexei
Director of Web Development - Farallon Geographics, Inc. -
