fix: resolve #469 — code.find(codeshift.Decorator) ignores decorators on class properties#703
Conversation
…corators on class properties Fixes facebook#469 Signed-off-by: ed-thuando <231172918+ed-thuando@users.noreply.github.com>
…corators on class properties Fixes facebook#469 Signed-off-by: ed-thuando <231172918+ed-thuando@users.noreply.github.com>
|
@ed-thuando is attempting to deploy a commit to the Meta Open Source Team on Vercel. A member of the Team first needs to authorize it. |
|
|
Hi @ed-thuando! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
Summary
fix: resolve #469 — code.find(codeshift.Decorator) ignores decorators on class properties
Problem
Severity:
Medium| File:src/matchNode.jsThe matchNode.js file likely contains logic to determine if a node matches a given type. Need to verify if it properly handles decorators on ClassProperty nodes.
Solution
Check if there's a type mapping that defines which node types can contain decorators, and ensure ClassProperty is included.
Changes
src/matchNode.js(modified)src/collections/Node.js(modified)Testing
Generated by ContribAI v6.0.0