Maddy Miller
Maddy Miller
My main issue with this is that "use" is conceptually different between many of the mechanics, and allowing a blanket "use" permission would encourage people to not understand what they're...
I wasn't saying your permission plugin would support it, I was saying that it's up to the permissions plugin to support it
I could possibly add this as a feature of pipes, being able to pipe into "trash". That'd make sense.
Make sure you don't have the bypass consumables permission
As discussed in Discord, this is due to limitations in the Spigot API, and cannot be resolved until CB5 where we will drop Spigot support and require Paper. This still...
Is there a reason you require a Dispenser for this? CraftBook has many systems that allow setting blocks based on the contents of containers.
This is scheduled for being fixed in CraftBook5. Due to the way it works at the moment, more fundamental changes need to occur and the WorldEdit API will be used...
IMO the main usecase for a rule like this over `no-restricted-syntax` is that it can have an auto-fixer when type information is available (replace the wildcard with all named exports),...
I feel that's somewhat of a poor reason to not have a linting rule. Linting rules exist to match preferences of a codebase, and for codebases that want this it...
In terms of consistency with `consistent-type-exports`, would it make sense to also have an option that will inline `type` rather than split, but for cases where all imports are types,...