Table not working if wrong drive is selected - Githubissues

atomicdata-dev / atomic-server

An open source headless CMS / real-time database. Powerful table editor, full-text search, and SDKs for JS / React / Svelte.

https://atomicserver.eu

MIT License

877 stars 42 forks source link

Table not working if wrong drive is selected #893

Closed joepio closed 3 days ago

joepio commented 1 month ago

Open a table from a different server, like so

I'm assuming this goes wrong because the /search query is sent to the "current drive" instead of the drive shown in the resource.

How we can solve this:

Always set current drive to opened resource

When opening a resource in a new drive, set that new drive as current one.

When clicking some external thing (e.g. looking at the "description" property) this means you lose your "home" context. Could be a bit bothersome. Perhaps we should add a "back" button? Or open external things in a modal?

Polleps commented 4 weeks ago

Tables does not use the search endpoint. Its probably the collection that takes the serverURL from the store instead of the resource