Skip to content

feat(rules): specify the Rule archetype pattern with OpenAPI 2.0 #16

@gregswindle

Description

@gregswindle

💡 TIP: Select the "Preview" Tab to help read these instructions.

1. Issue type

Type the letter "x" in the "checkbox" the best describe this issue.

  • Feature: I'm requesting an enhancement.

2. User story summary

Describe what you want to accomplish and in what role/capacity, and why it's important to you.
EXAMPLE:
As a Job Applicant,
I want to submit my resume
In order to be considered for a job opening.

As an API consumer and producer,
I want to explicitly define rules and conditional logic independent of source code and database triggers,
In order to immediate define, execute, review, reuse, and quickly establish personalization and business constraints.

3. Acceptance criteria

Replace the examples below with your own imperative, "true/false" statements for the behavior you expect to see, or the behavior that would be true if there were no errors (for defects).

  • 1. TBD
  • 2. TBD
  • 3. {criterion-three}
  • 4. {criterion-four}

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions