atomic-server

atomic-server copied to clipboard

## Related Issues closes #433 ## Checklist - [ ] Add changelog entry linking to issue, describe API changes - [x] Add or update tests if needed - [x] Update...

AlexMikhalev

Svelte 5 reactivity is very complicated and convoluted. Its initial simplicity is misleading when working with complex data structures that are not designed with svelte in mind, like our Resource...

Polleps

[Paths](https://docs.atomicdata.dev/core/paths.html) are a way to fetch resources multiple levels deep. They are also a way to identify anonymous resources. Currently we allow the use of property short-names in place of...

Polleps

Should sorting filter a value?

1

Because of how I've implemented sorting, sorting now results in a _filtered_ list. If the sorter property value is not present in a resource, it will be left out of...

joepio

Plugins (Endpoints / class extenders) can have query parameters. For example, the `/search` endpoint. The problem of this, is that the front-end tries to subscribe to every single `?query-param`, but...

joepio

AtomicData makes it easy to re-use classes and properties from _external_ sources. That's an important part of the proposition, but relying on fetching individual HTTP requests for classes and properties...

joepio

While @Polleps was working on a migration to use JSON values #658, he noticed that re-builiding the index `Db::build_index` was very slow. 100ms per resource, where this should be at...

joepio

Some time ago I implemented transaction logic in AtomicServer. However, I still kept the `add_resource_opts` and the `::set_propvals` methods, in addition to the new `apply_transaction` logic. Although I don't think...

joepio

Find a way to replace eslint + prettier

1

I strongly dislike having two tools that could disagree on formatting. Doesn't play nice with Zed either. Eslint itself is insanly slow and needs a lot of config. Also, our...

joepio

The agent subject takes up almost all available space. It should be truncated

Polleps