-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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.
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
Fix issue #21065 getInspectorDataForViewTag is not a function #21237
Conversation
fix renderer.getInspectorDataForViewTag is not a function
Fix renderer.getInspectorDataForViewTag is not a function when try Toggle Inspector
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up 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 the corporate CLA signed. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
eslint
found some issues. You may run yarn prettier
or npm run prettier
to fix these.
Libraries/Inspector/Inspector.js
Outdated
const inspectorData = renderer.getInspectorDataForViewTag(touchedViewTag); | ||
if (inspectorData.hierarchy.length > 0) { | ||
return inspectorData; | ||
if (Object.prototype.hasOwnProperty.call(renderer, 'getInspectorDataForViewTag')) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
prettier/prettier: Replace Object.prototype.hasOwnProperty.call(renderer,·'getInspectorDataForViewTag')
with ⏎······Object.prototype.hasOwnProperty.call(⏎········renderer,⏎········'getInspectorDataForViewTag',⏎······)⏎····
Generated by 🚫 dangerJS |
Would you mind adding a test plan to your PR? |
@TranLuongTuanAnh thank you for your PR. Unfortunately, there is no explanation for this pull request in terms of how to reproduce this issue and what it actually fixes. Since there hasn't been a reply in more than a month. I'm going to close this PR, but I am happy to reopen and land it if you can add the information back. |
This should be reopened. See here: #21065 |
@th317erd would you mind opening a new PR? Please make sure to address the feedback from this thread when doing so. |
No @hramos, this PR is fine, and just needs to be reopened. If you need another PR request from the author just ask. Besides, it peeves me greatly to try and follow Facebook's stringent and ridiculous "Community Guidelines". They essentially bitch-slap their community members all the time by closing PRs, closing and locking legitimate bug requests, being rude, and generally having the all around "don't give a shit about our community" attitude. I am not eager to help out the Facebook community because of this, and because nearly every interaction I have had with one of their developers has been a negative experience. If they don't want the help from the community (that IMHO is blatantly obvious through their actions and attitude), that is Facebook's problem, not mine. Sorry, normally with any other community I would be happy to help, not this time. |
@th317erd thanks for making me realize I missed the issue number in the title, oops! I edited the summary to add the issue as well. I'm sorry that we disappointed you in the past and hope we can win back your trust in the future. We are working hard on getting React Native open source into a manageable state but it will take a while. @TranLuongTuanAnh Unfortunately I cannot land your fix unless you sign the CLA. Please go to https://code.facebook.com/cla to sign it so we can land this change. Thank you :) |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cpojer is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
Thanks for the quick turnaround. Landing this PR now. |
Thank you @cpojer! |
…facebook#21237) Summary: Fix renderer.getInspectorDataForViewTag is not a function when try Toggle Inspector Fixes facebook#21065 Release Notes: -------------- [BUGFIX] [MINOR] [/react-native/Libraries/Inspector/Inspector.js] Pull Request resolved: facebook#21237 Differential Revision: D13838339 Pulled By: cpojer fbshipit-source-id: 363a4beba211e7868395578c7941cbda119bc753
I'm sorry, I got it under way. |
Fix renderer.getInspectorDataForViewTag is not a function when try Toggle Inspector
Fixes #21065
Release Notes:
[BUGFIX] [MINOR] [/react-native/Libraries/Inspector/Inspector.js]