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.

Sign up for GitHub

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

Jump to bottom

Recognise tsx template literals without substitutions #107

Merged
merged 4 commits into from
Oct 10, 2022
Merged

Recognise tsx template literals without substitutions #107

merged 4 commits into from
Oct 10, 2022

Conversation

aslakhellesoy
Copy link
Contributor

🤔 What's changed?

TypeScript template strings are recognised as strings.

⚡️ What's your motivation?

Fix #101

🏷️ What kind of change is this?

  • ⚡ New feature (non-breaking change which adds new behaviour)

♻️ Anything particular you want feedback on?

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

@aslakhellesoy aslakhellesoy changed the title Tsx template literal Recognise tsx template literals without substitutions Oct 10, 2022
@aslakhellesoy aslakhellesoy merged commit ef820df into main Oct 10, 2022
@aslakhellesoy aslakhellesoy deleted the tsx-template-literal branch October 10, 2022 20:31
@aslakhellesoy aslakhellesoy mentioned this pull request Oct 10, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Plugin doesn't recognize steps that use `` instead of '' or ""
1 participant
@aslakhellesoy