atomic-data-browser icon indicating copy to clipboard operation
atomic-data-browser copied to clipboard

This repo is no longer used! Code is moved to Atomic-Server

Results 102 atomic-data-browser issues
Sort by recently updated
recently updated
newest added

These might be two separate issues, but they could be related. A refactor might tackle both at once. ## Dialogue needs additional click to get focus - Open class editor...

I still sometimes get the `unauthorized` screens. I just had it when I had two cookies - one for `atomicdata.dev` and one for `staging.atomicdata.dev`. Removing the cookies fixed the issue....

- [x] see children of children in the sidebar - [x] collapse / open parents in the sidebar - [ ] change the parent of a resource by dropping a...

The repo size is about 1.5GB, most of which is taken up by old dependencies from `.yarn/cache`. There are tools that help to remove stuff from git history, but it...

- [Importer](https://github.com/atomicdata-dev/atomic-data-browser/issues/300), class and property are very 'techical' resources. Class and Property are even more low-level, as they make up parts of other resources. Should we show them here? Thanks...

- Create a resource - Go to edit form - Advanced - Edit parent - Save - No effect? Thanks to @adileo

Importing can now happen everywhere, to every parent, so it should not be linked to an `importer` instance anymore. We should make importing available from context menu. The view itself...

When you want to search in a resource selector, we now _always_ default to `atomicdata.dev`. There are several cases where you want to search your _own_ server, instead. I think...

Currently, the selected Drive does not have anything to do with the URL. Sometimes this is good, but it can also be confusing. Example: - Set [any custom drive](https://atomicdata.dev/drive/xzpv34r5ibr) as...

- Use atomic-server from [this pr ](https://github.com/atomicdata-dev/atomic-data-rust/pull/580). - Open a page (on 9883, not vite) - Refresh the page - In the drive resource: `Could not parse JSON from fetching...