Hi! While reading the source I spotted a number of misspellings in JSDoc and
inline comments across motion-utils, motion-dom, and framer-motion. They
surface in IDE tooltips and hurt readability of the explanatory comments, so
I'd like to contribute the fixes.
What
19 misspellings across 15 files — comment/JSDoc only, no logic, types, or
behavior change (19 insertions / 19 deletions, one-to-one word swaps). A few
examples:
motion-utils/src/pipe.ts — linearily → linearly
motion-dom/src/render/VisualElement.ts — inherting → inheriting (×2)
framer-motion/.../use-visual-element.ts — situtation → situation
motion-dom/.../create-projection-node.ts — calculcated/relavent/recalcualte → calculated/relevant/recalculate
Full list is in the branch (below).
Where
Ready on a branch in my fork: AlexRixten:docs/fix-comment-typos
main...AlexRixten:docs/fix-comment-typos
How to proceed
I tried to open a PR directly, but the repo's PR creation policy is
collaborators-only, so I can't. I'm happy to either:
- open the PR if I'm added as a collaborator, or
- have a maintainer merge the branch from the fork directly.
Either works — just let me know. Thanks!
Hi! While reading the source I spotted a number of misspellings in JSDoc and
inline comments across
motion-utils,motion-dom, andframer-motion. Theysurface in IDE tooltips and hurt readability of the explanatory comments, so
I'd like to contribute the fixes.
What
19 misspellings across 15 files — comment/JSDoc only, no logic, types, or
behavior change (19 insertions / 19 deletions, one-to-one word swaps). A few
examples:
motion-utils/src/pipe.ts—linearily→linearlymotion-dom/src/render/VisualElement.ts—inherting→inheriting(×2)framer-motion/.../use-visual-element.ts—situtation→situationmotion-dom/.../create-projection-node.ts—calculcated/relavent/recalcualte→calculated/relevant/recalculateFull list is in the branch (below).
Where
Ready on a branch in my fork:
AlexRixten:docs/fix-comment-typosmain...AlexRixten:docs/fix-comment-typos
How to proceed
I tried to open a PR directly, but the repo's PR creation policy is
collaborators-only, so I can't. I'm happy to either:
Either works — just let me know. Thanks!