It actually does nothing. What works is setting allowUnauthenticated on the Collection to an array of methods (e.g. allowUnauthenticated: ['post', 'put'])
Do we want to be able to define allowUnauthenticated in both places? If so, we'll need to fix it so that defining it on CollectionOperationConfig works. We should also set allowUnauthenticated to a default in Collection for the purposes of documentation. It might make sense to change it to allowedUnauthenticatedMethods to avoid confusion since it isn't boolean.
This issue is also in the collection-overhaul branch.
CollectionOperationConfig.allowUnauthenticated
looks like it should allow unauthenticated requests to the operation if set totrue
.It actually does nothing. What works is setting
allowUnauthenticated
on theCollection
to an array of methods (e.g.allowUnauthenticated: ['post', 'put']
)Do we want to be able to define
allowUnauthenticated
in both places? If so, we'll need to fix it so that defining it onCollectionOperationConfig
works. We should also setallowUnauthenticated
to a default inCollection
for the purposes of documentation. It might make sense to change it toallowedUnauthenticatedMethods
to avoid confusion since it isn't boolean.This issue is also in the
collection-overhaul
branch.