Skip to content

Ensure user-defined preconditions run after speced.def's #90

@vemv

Description

@vemv

Problem statement

Given a speced defn with user-provided :preconditions:

  • both sources of preconditions will be correctly merged; but
  • the user ones take precedence.

This means that more opaque errors can pop up: type (speced's) errors are more straightfoward than a business-specific one (user's) that failed for 'type' reasons.

Task

Merge preconditions in a specific order.

Metadata

Metadata

Assignees

No one assigned

    Labels

    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