Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Caveats are restrictions, yet empty Caveats mean "nothing's allowed" #170

@andrewzhurov

Description

@andrewzhurov

This feels contrary to what Caveats are meant to express.

Both

{"dns:example.com?TYPE=TXT": {
    "crud/create": [{}]
  }}

and

{"dns:example.com?TYPE=TXT": {
    "crud/create": []
  }}

Intuitively, to me, mean that nothing's restricted.
Whereas if somebody wish to express "nothing's allowed" they could simply not include the capability in the first place.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions