Skip to content

🚀 Feature: Add an option to disable special character escaping #63

@JoshuaKGoldberg

Description

@JoshuaKGoldberg

This pulls together #2, #26, #45, #46:

I think the "right" (or: least unexpected) way would be to add an option with a not-very-savory name like escapeSpecialCharacters. The option would default to:

  • true when called for a template literal string
  • false when called as a function

Proposal:

  • Let's add this option in separately from fix: consume first level of escaping of $ and { characters #46, to resolve this issue and 26
  • I can release a new minor version that includes this option and 26
    • I'm a little hesitant to merge that PR before this option is in, in case folks are relying on the existing behavior

Thoughts @G-Rath @sirian?

Metadata

Metadata

Labels

type: featureNew enhancement or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions