Skip to content
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

Closed
wants to merge 5 commits into from

Conversation

TranLuongTuanAnh
Copy link
Contributor

@TranLuongTuanAnh TranLuongTuanAnh commented Sep 21, 2018

Fix renderer.getInspectorDataForViewTag is not a function when try Toggle Inspector

Fixes #21065

Release Notes:

[BUGFIX] [MINOR] [/react-native/Libraries/Inspector/Inspector.js]

fix renderer.getInspectorDataForViewTag is not a function
Fix renderer.getInspectorDataForViewTag is not a function when try Toggle Inspector
@facebook-github-bot
Copy link
Contributor

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!

Copy link

@analysis-bot analysis-bot left a 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.

const inspectorData = renderer.getInspectorDataForViewTag(touchedViewTag);
if (inspectorData.hierarchy.length > 0) {
return inspectorData;
if (Object.prototype.hasOwnProperty.call(renderer, 'getInspectorDataForViewTag')) {

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',⏎······)⏎····

@pull-bot
Copy link

Warnings
⚠️

📋 Test Plan - This PR appears to be missing a Test Plan.

⚠️

📋 Release Notes - This PR may have incorrectly formatted Release Notes.

Generated by 🚫 dangerJS

@react-native-bot react-native-bot added Missing Test Plan This PR appears to be missing a test plan. Missing Changelog This PR appears to be missing a changelog, or they are incorrectly formatted. 🔶Components labels Sep 21, 2018
@hramos
Copy link
Contributor

hramos commented Dec 11, 2018

Would you mind adding a test plan to your PR?

@hramos hramos added ✅Changelog and removed Missing Changelog This PR appears to be missing a changelog, or they are incorrectly formatted. labels Jan 15, 2019
@cpojer
Copy link
Contributor

cpojer commented Jan 22, 2019

@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.

@cpojer cpojer closed this Jan 22, 2019
@th317erd
Copy link

This should be reopened. See here: #21065

@hramos
Copy link
Contributor

hramos commented Jan 26, 2019

@th317erd would you mind opening a new PR? Please make sure to address the feedback from this thread when doing so.

@th317erd
Copy link

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.

@cpojer cpojer reopened this Jan 28, 2019
@cpojer
Copy link
Contributor

cpojer commented Jan 28, 2019

@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 :)

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jan 28, 2019
@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@facebook-github-bot facebook-github-bot added the Import Started This pull request has been imported. This does not imply the PR has been approved. label Jan 28, 2019
Copy link
Contributor

@facebook-github-bot facebook-github-bot left a 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.

@cpojer
Copy link
Contributor

cpojer commented Jan 28, 2019

Thanks for the quick turnaround. Landing this PR now.

@th317erd
Copy link

Thank you @cpojer!

matt-oakes pushed a commit to matt-oakes/react-native that referenced this pull request Feb 7, 2019
…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
@tkow
Copy link

tkow commented Mar 5, 2019

Is any progress?

I'm sorry, I got it under way.
46f3285

@hramos hramos added the Merged This PR has been merged. label Mar 8, 2019
@react-native-bot react-native-bot removed the Import Started This pull request has been imported. This does not imply the PR has been approved. label Mar 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Merged This PR has been merged. Missing Test Plan This PR appears to be missing a test plan.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants