Juliette
Juliette
**Action plan**: 1. Create a test case to proof or disproof that there is a bug. 2. If a failing test can be created: fix the bug. 3. Otherwise close...
Also #759 (duplicate)
Before we actually action this, we should have a good look at the security implications of allowing access to the `$handle` (not just here).
@gdarko It's kind of hard to review code which is littered with unaddressed (automated) comments....
Hiya @JamieSlome and @ranjit-git, Thanks for bringing this to our attention. We'll get that sorted soonish (need to figure out an email address which can be used). In the mean...
For WordPress itself, HackerOne is definitely the preferred way. For Requests, we'll have a discussion about this in the near future, but until otherwise decided, HackerOne will work for the...
Just checking: did the issue ever get reported ? If so, would you mind posting a link so those of us who have access to the WP HackerOne account can...
@ShivamYuvraj Thank you for contributing. Would it be possible to add some unit tests for this change ?
Ideas: * Add a cache interface and separate the caching from the IRI class ? * Add a cache property/properties with appropriate cache setting/clearing options ? This should be looked...
Note for the next iteration of this PR: For testing the correct functioning of this change, the PHPUnit 9.3+ `Assert::assertIsClosedResource()` assertion can be used. This assertion is [polyfilled by the...