- Conventions and Terminology
- Development Tools
So you want a feature to enter Fabric? Well then - here's a brief guide on how to best propose a feature in a way which won't get lost in noise and give some measurable results.
There are many projects in the Fabric toolchain, and all of them welcome different types of content (when in doubt, ask us in chat!):
However, if your idea doesn't fit on the above list, fear not! There are other ways to share your standard with the world:
In short: Ask someone more knowledgeable in chat if the idea is even worth pursuing for Fabric. This can be skipped, of course - if you don't mind wasting a bit extra time in exchange for wider insights.
Yes. Open an issue. Like, on the relevant GitHub project. We do often miss chat messages, etc. - while they're fine for initial surveying and discussion, they're not fine for keeping a track record.
(cue all developers arguing for 100 comments on the meaning of a 5-line patch)
Just wait until a clear direction/design is decided upon.
Now that you know what to do, put it into code! (Of course, the issue creator and the pull request developer do not have to be the same person. If you're lucky, one of the devs might even do the ground work for you!)
Make sure your code can compile. Also make sure
checkstyle is happy and run a
(have you met Player yet?)
You are almost there! Now your pull request goes into last call where extra scrutiny may be applied before accepting the pull request.
Rejoice. Your feature is now a part of the Fabric hype train.