-
trying to use plugin and hereby following README.md.
When exucuting
./gradlew runIde
getting
"Plugin Repositories (could not resolve plugin artifact 'org.gradle.toolchains.foojay-resolver…
-
### Body of the issue
https://github.com/inventree/inventree-docs/issues/427
It would be great to add the naming "conventions" discussed in https://github.com/wolflu05/inventree-bulk-plugin/issues…
-
Hey! It’s usually a convention to name Bevy plugins using the “bevy_*” pattern. What do you think about renaming it?
Edit: Very cool plugin btw, ty 👍🏼
-
## What?
Update PHP tests to follow WP core conventions.
Reference docs: https://make.wordpress.org/core/handbook/testing/automated-testing/writing-phpunit-tests/#test-classes
Reference source: htt…
-
### Describe the issue
Android Studio actions (clean, build, rebuild, etc) do not use project defined gradle wrapper. Using terminal or running configurations works as expected.
### Can you reliab…
-
i noticed that jekyll plugins (and mostly themes) have defined naming conventions:
🔗 https://jekyllrb.com/docs/themes/#installing-a-theme
- `jekyll-` prefix for all jekyll plugins (perhaps postf…
-
# Requested Update
### Description
We should come up with standard naming conventions for all plugins, families, and interfaces.
### Background and Motivation
Current names:
- Can be anythin…
-
https://blog.sapzil.org/2022/03/04/gradle-convention-plugins/
-
### Current Behavior
When an error happens in a convention plugin, the error location is not correct, e.g.
```text
* What went wrong:
An exception occurred applying plugin request [id: 'firepla…
bric3 updated
3 months ago
-
Should newly created projects which use Gradle be configured with Gradle convention plugin(s) by default?