Skip to content

clarity issues #6

@aaronkaplan

Description

@aaronkaplan

I think it's a good start but the draft could need some more work w.r.t to clarity:

  • is it allowed to define other fields ad-hoc?
  • If yes, where to register these fields?
  • rationale: why are we doing this? Give two, three use-cases (just makes it clearer for the user what cool things he/she could do with that format)
  • what fields are a MUST?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions