Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CCK: Reconcile attachments #69

Merged
merged 5 commits into from
Oct 31, 2023
Merged

CCK: Reconcile attachments #69

merged 5 commits into from
Oct 31, 2023

Conversation

luke-hill
Copy link
Contributor

🤔 What's changed?

attachments are now is consistent for ruby/js.

⚡️ What's your motivation?

Goes towards completion of issue in tracker

🏷️ What kind of change is this?

  • 🏦 Refactoring/debt/DX (improvement to code design, tooling, documentation etc. without changing behaviour)
  • 🐛 Bug fix (non-breaking change which fixes a defect)

♻️ Anything particular you want feedback on?

Do we need to fix anything else (I'm deliberately not regenerating the ndjson yet because there are a bunch of these that will need re-generating each time).

To avoid conflicts I'll re-generate once after merging several of these fixes

📋 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.

This text was originally generated from a template, then edited by hand. You can modify the template here.

Copy link
Contributor

@davidjgoss davidjgoss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On this PR and others we have made a lot of changes but the need for all of them isn't clear. I think in general we should be keeping the scope of changes to a minimum, especially where it would reduce coverage or require existing implementations to redo steps.

Bear in mind the fake-cucumber steps and Ruby steps are not equal constituents - the former are the reference point and implementations are in theory supposed to conform.

When a JPEG image is attached

Scenario: Attaching images in examples
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why have we removed this one?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've just simplified the code. Examples tables are covered in a diff feature

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are but I don't think that one includes attachments?

@luke-hill
Copy link
Contributor Author

@davidjgoss fixed up the before hook issue and made a new issue here: #83 for us to investigate this post reconciliation work.

I believe the other 2 items are just redundant pieces of code, hence removing them and trying to keep everything clean and lean

@luke-hill luke-hill merged commit 2612803 into main Oct 31, 2023
7 checks passed
@luke-hill luke-hill deleted the bugfix/reconcile_attachments branch October 31, 2023 17:18
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.

2 participants