Skip to content

Property statement should handle more than just string #50

Description

@tpluscode

Current the property rule only accepts STRING values

ExpectModifier 'Property' name=Identifier (expectation=STRING)?

I would like to at least also support

  • integers, decimals, booleans
  • numeric comparison
  • regex
Expect Property "foo" true
Expect Property "age" Less Than 21
Expect Property "extension" Matching "$.docx?"

Additionally hydra could have special type assertion check rdf:type property, used with URIs

Expect Type hydra:Collection

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions