Conversation
Define what optional functions are actually implemented in this controller
Fix property name collision with orbitdb-access-controller
orbitdb-access-controller has both grant and revoke implemented
eth-contract/deposit-contract has grant and revoke
eth-contract/cool-contract has grant and revoke
@phillmac Thanks for opening a PR. Can you elaborate on what you're trying to accomplish? Also note that none of the access controllers currently support key revocation |
Basically from the api standpoint, I have no visibility into the grant / revoke functions that are actually present on a given controller. It'd be useful to have the ability to report for e.g. If this controller has |
@phillmac could the same be achieved by calling the capability of interest in a |
@shamb0t If the functions were just purely undefined and generated errors that'd be great, because the error would be feedback that the api call failed. |
As you said there would be some interface overhead in maintaining a list of what controllers have what functions. A better solution would be very welcome! |
@phillmac ah yes ofc they are already in the interface....hmm perhaps a quick fix could be changing |
That'd be a lot better. I'll make another pr and close this one? |
@phillmac that would be great! |
Define what optional functions are actually implemented in this controller, e.g. grant / revoke as a public static property