...
Currently, the library does not check for or use relative URLs. This could be an additional feature implemented in the future.
Currently, the library has no way to programmatically manipulate storage creation/deletion inside a Solid server, due to using Inrupt’s Javascript API which does not have methods for creating/deleting storage. Inrupt has mentioned they plan to implement this feature in the future, which would then allow this library to also create and delete storage inside a Solid server after some modification.
Currently, the
pods:store()andpods:overwrite()functions have a size limit for the originURL parameter when using adatascheme as input.Currently, a pico and storage exist in a Many-to-1 relationship (or Many-to-0 relationship) as any number of picos may connect to a single storage. In the future, the library could be expanded to include picos connected to multiple Solid storages.
We had a plan to create a function that would take in the name of any command in Inrupt’s Javascript client library and then call that function. We did not have time to implement this function, but it may be useful to implement this in the future.
A small implementation note: automatic authentication is currently implemented with a lot of duplicate code. We would have preferred to use the template pattern to do this, but we ran out of time. This may be something to implement for future improvements to the module.
File names are currently acquired by splitting the destination URL at the last slash and taking the right portion of that split. This unfortunately includes any query parameters in the URL which can cause issues and needs cleaning.
Resource access management needs expansion (functionality to look at a specific agent’s permissions, and functionality to look at a specific agent’s/the public’s permissions individually).
Documentation is assuming your web ID (identified via client ID and client secret) has the appropriate access permissions on the Solid server.
...