Skip to content

feat(contracts): add a availableExpectations field #304

New issue
New issue
Closed
Feature
#306
Closed
feat(contracts): add a availableExpectations field#304
Feature
#306
Assignees
guzmud
Labels
criticalCritical issue to fix ASAP.featureType: new feature or capability (feat:).solvedResolved (should be linked to the solving PR).

Description

@guzmud
Ferdinand (guzmud)
opened on Jul 15, 2026

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

  1. Ferdinand (guzmud)
    added the
    Feature
    issue type on Jul 15, 2026
  2. Ferdinand (guzmud)
    added
    featureType: new feature or capability (feat:).
    on Jul 15, 2026
  3. github-actions
    added
    needs triageNeeds triage from the Filigran product team.
    on Jul 15, 2026
  4. Ferdinand (guzmud)
    added
    criticalCritical issue to fix ASAP.
    and removed
    needs triageNeeds triage from the Filigran product team.
    on Jul 15, 2026
  5. Ferdinand (guzmud)
    marked this as blocking on Jul 15, 2026

  6. guzmud commented on Jul 15, 2026

    @guzmud
    Ferdinand (guzmud)
    on Jul 15, 2026
    MemberAuthor

    Note for reviewers and bystanders: the issue regarding DRY has been taken into account, a follow-up issue have been written here #305

  7. Ferdinand (guzmud)
    added a commit that references this issue on Jul 15, 2026

    fix(contracts): missing type hint leading to issue in inheritance (#304)

    b8f68a0
  8. Ferdinand (guzmud)
    self-assigned this
    on Jul 16, 2026
  9. Samuel Hassine (SamuelHassine)
    added a commit that references this issue on Jul 18, 2026

    feat(contracts): adding the new availableExpectations field (#304) (#306

    3ca50c3
  10. Samuel Hassine (SamuelHassine)
    closed this as completedin #306on Jul 18, 2026
  11. github-actions
    added
    solvedResolved (should be linked to the solving PR).
    on Jul 18, 2026
  12. github-actions
    added this to the 1. Now milestone on Jul 18, 2026
  13. Romuald Lemesle (RomuDeuxfois)
    modified the milestones: 1. Now, 0. Candidate on Jul 20, 2026
  14. Filigran Automation (Filigran-Automation)
    modified the milestones: 0. Candidate, Release 3.260805.0 on Aug 5, 2026
  15. corinnekrych (corinnekrych)
    removed this from the Release 3.260805.0 milestone on Aug 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

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

Type

Feature

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions