You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed during several dev meetings, the semantics of the currently implemented acl:defaultForNew predicate are slightly off, and are more appropriate to be named acl:default.
The consensus was to rename existing usage of acl:defaultForNew predicate in the ACLs of Gold and LDNode installations. (And also have a transitionary period where the server supports both predicates for a few versions, and just gives a deprecation warning for defaultForNew).
To do:
implement support for acl:default in solid-permissions (it should also handle legacy acl:defaultForNew)
As discussed during several dev meetings, the semantics of the currently implemented
acl:defaultForNew
predicate are slightly off, and are more appropriate to be namedacl:default
.The consensus was to rename existing usage of
acl:defaultForNew
predicate in the ACLs of Gold and LDNode installations. (And also have a transitionary period where the server supports both predicates for a few versions, and just gives a deprecation warning for defaultForNew).To do:
acl:default
insolid-permissions
(it should also handle legacyacl:defaultForNew
)acl:default
insolid-ui/src/acl.js
acl:default
innode-solid-server
(switch default account template to use it)The text was updated successfully, but these errors were encountered: