| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
- Handle plugin errors in permission.ask hook and fallback to ask - Add test cases for allow, deny, and error paths in plugins - Add documentation for empty ruleset on plugin denial
|
The following comment was made by an LLM, it may be inaccurate: I found one potentially related PR: Related PR:
The other search result (#12520) is unrelated to permissions. Since #19453 exists, you may want to check if it was closed/abandoned and whether your PR supersedes it or builds upon it. |
Sorry, something went wrong.
Thanks for the pointer! I reviewed #19453. While both PRs aim to wire the permission.ask hook, this new PR (#30509) supersedes it by addressing critical safety and
I believe this makes it a safer and more complete implementation. Please let me know what you think! |
Sorry, something went wrong.
|
Why is this not merged yet? Who needs to approve this? |
Sorry, something went wrong.
|
Please accept this pull request as soon as possible! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Issue for this PR
Closes #7006
Closes #22311
Type of change
What does this PR do?
Properly wires the permission.ask plugin hook by adding Plugin.trigger right before the prompt. This allows plugins to
intercept and return allow or deny. It passes a shallow copy of the request info to prevent accidental mutation by plugins,
and uses Effect.catchCause so plugin defects don't crash the core flow.
How did you verify your code works?
Injected a mocked PluginLayer into next.test.ts and added specific test cases for plugin allow, deny, and exception
paths. All 82 tests pass successfully.
Screenshots / recordings
N/A
Checklist