Potential typo in `LegacyITransforamtionOptions` interface name

Open
#606 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript

Research direction

Start in src/types/types.ts at the LegacyITransforamtionOptions declaration and check how the type is exported and referenced. Confirm whether the spelling is accidental and whether existing users need a deprecated compatibility export. Done means the naming decision is documented and the public type exports preserve compatibility where required.

Written by the indexing model from the issue text.

Description

Couldn't see an issue (open or closed) around this so unsure if it's known or not.

Instead of "Transformation" this interface is called "Transforamtion".

If the spelling does get changed, it might still be a good idea to re-export the type as "Transforamtion" and mark it deprecated, otherwise it could break repos that are importing / using the misspelled version.

If leaving as is (or if it's intentional), this issue can show that it's known and not changing I guess.

Dominant language
HTML
Stars
56
Forks
11
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudinary/js-url-gen

All issues in cloudinary/js-url-gen

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.