Skip to content

feat(contracts): add a availableExpectations field #304

Description

@guzmud

Backstory

Following the changes made to the injector contract with OpenAEV-Platform/openaev#5148 and OpenAEV-Platform/openaev#5554, the injectors are expected to send back two distinct lists availableExpectations ("@param availableExpectations the full list of selectable expectations") and predefinedExpectations ("@param predefinedExpectations the default expectations to include").

Current workaround

None.

Proposed solution

The ContractExpectations class must be updated with a new availableExpectations similar to predefinedExpectations in typing.

Activity

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

Metadata

Metadata

Labels

criticalCritical issue to fix ASAP.featureType: new feature or capability (feat:).solvedResolved (should be linked to the solving PR).

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions