Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[DomCrawler] Fix null namespace issue in Crawler#39474
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
[DomCrawler] Fix null namespace issue in Crawler#39474
Uh oh!
There was an error while loading.Please reload this page.
Conversation
carsonbot commentedDec 11, 2020
Hey! I see that this is your first PR. That is great! Welcome! Symfony has acontribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
derrabus commentedDec 11, 2020
Thank you@prosalov. |
In this case
issetmay cause an issue if null value would be stored in$this->namespacesor$this->cachedNamespaces, but never fetched, as if condition would return false. This PR is for 5.x, because namespace caching was introduced recently (#39097).