-
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
react-native\packages\react-native\Libraries\Blob\URL.js Changes #48333
base: main
Are you sure you want to change the base?
Conversation
Hi @bobbysharma05! 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 [email protected]. Thanks! |
|
Hi @bobbysharma05, thanks for working on this. |
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.
Code changes look good to me, but the PR is missing information in the Description.
We can't import without Summary, Changelog and TestPlan
Also, the test_js signal is failing, can you have a look at it? |
ok sir I will look into it and also add the summary. |
Sir I am new to the open source. Could you please help me in which part I am getting stuck. |
When a new pr is open, we provide a template that has to be filled. For the Changelog, specifically, it has to follow a predefined format, which is described here. For this pr, it should be something like:
For the failures, you can click on the failed signals in the github UI and read through the logs, looking for the errors (the search function is your friend). For example, the linter says that the community-cli-plugin has been built and it should not. If you inspect the changed files, you see that you committed a package.json that should not be committed. The test_js says that there is an invalid expression at line 25 of the URL.js file. Build_android failure is related to the failure for the linter, so it should be fixed by reverting the changes in the |
SUMMARY
The URL class was refactored to handle blob URLs more effectively, improving URL construction and parsing. Changes include better error handling in the createObjectURL method and the addition of functions to extract URL components like username, host, and protocol.
Changelog:
Test Plan: