Setting a token should perform a "reload", not having a token may need to disable functionality #29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It is nice that the site is quasi fully usable without a token. At the same time, it is also frustrating.
Not having to set a token frequently leads to not setting a token at the start of a procedure, but only later for submission.
People that edit things without having a token, will eventually loose the content of their session, and be angry.
When I have a class "tab" open, and I set a token, I still need to manually reload the page to have the new (potential) data availability reflected on the page.
I have no concrete suggestion what to change. Maybe we should distinguish a "browse" mode from an "edit" mode, and the latter requires a token. But, pending the outcome of https://github.com/christian-monch/dump-things-server/issues/67 a token may not be sufficient. It may need to be a "write" token for the target collection.
Fixing this would be an easy win here, we can just reload the process to generate the current view (e.g. a list of
Personrecords) if a token is set while on that view.The rest seem like issues to be resolved as we use
shacl-vueinstances more and more for particular use cases. It has likely already evolved with our introduction of multiple service base-urls for read/write purposes.