Skip to content

Conversation

mpkorstanje
Copy link
Contributor

⚡️ What's your motivation?

In #76 Lineage became part of the public API. This removes the need for various queries that depend on the lineage or the lineage reducer.

To ensure test coverage remains the NamingStrategyAcceptanceTest was added.

Fixes: #82.

🏷️ What kind of change is this?

  • 🏦 Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)

📋 Checklist:

  • I agree to respect and uphold the Cucumber Community Code of Conduct
  • I've changed the behaviour of the code
    • I have added/updated tests to cover my changes.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.
  • Users should know about my change
    • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

In #76 Lineage became part of the public API. This removes the need for
various queries that depend on the lineage or the lineage reducer.

To ensure test coverage remains the `NamingStrategyAcceptanceTest` was
added.

Fixes: #82.
@mpkorstanje mpkorstanje mentioned this pull request Jul 9, 2025
7 tasks
clrudolphi added a commit to clrudolphi/query that referenced this pull request Jul 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clean up Lineage dependent methods from Query
1 participant