Joachim Van Herwegen
Joachim Van Herwegen
As discussed in #628. Currently the PUT/PATCH/DELETE functions return an array of ResourceIdentifiers indicating what was changed. It would be nice if instead a metadata object was returned. We can...
### Updated bug report with steps to reproduce With a default server ``` npm start ``` and the following client steps ``` curl -s https://csarven.ca/linked-research-decentralised-web > thesis.html curl -X PUT...
Related to discussion in #951. Since the memory store is going to start from a different template (this statement should be true after resolving #951), we can put even more...
This is mostly based on my knowledge of the code since I didn't test this yet. Let's assume we have a routing resource store that writes RDF data to a...
The registration form does not support the creation of dynamic pods as there is no way to choose a template. Its behaviour is already supported though since you can do...
How dynamic pods currently work: * On server start the dynamic config gets read and for every entry a store gets instantiated. * All these stores are put in a...
The latest version of the conformance test harness added an `--ignore-failures` option which we could use to make it so it can be run when doing a PR without blocking...
`DataAccessorBasedStore` is the store responsible for the "main" Solid behaviour of resources on CRUD requests. The main issue is that this class does a lot, and only works with `DataAccessors`....
There are several places where the IdP codes uses normal Errors instead of HttpErrors. In several places this is not relevant as those classes would be called by the `oidc-provider`...
There are many places where we use the N3.js Datafactory to create terms. There are also still several places where we use `@rdfjs/data-model` for the same reason. We should create...