| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Test Results 84 files ±0 84 suites ±0 13s ⏱️ ±0s Results for commit f1b833b. ± Comparison against base commit c3c3f23. This pull request removes 1 and adds 2 tests. Note that renamed tests count towards both.org.incendo.cloud.PermissionTest ‑ testPermittedNodeFollowingNotPermittedNode() org.incendo.cloud.PermissionTest ‑ [1] expectedException=class org.incendo.cloud.exception.NoPermissionException, settings=[] org.incendo.cloud.PermissionTest ‑ [2] expectedException=class org.incendo.cloud.exception.InvalidSyntaxException, settings=[HIDE_COMMAND_EXISTENCE] ♻️ This comment has been updated with latest results. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Adds an option so that when the sender is permitted to use a following or preceding node to the one parsed, an invalid syntax exception is returned instead of no permission. Maybe this option should also convert other no permission exceptions to unknown command? Or users could do that via the exception handling system.
Should this be expanded to invalid sender exceptions as well? (probably)