Thanks for wanting to contribute! There are many ways to contribute and we appreciate any level you're willing to do.
Need some new functionality to help? You can let us know by opening an issue. It's helpful to look through all issues in case its already being talked about.
Please let us know about what problems you run into, whether in behavior or ergonomics of API. You can do this by opening an issue. It's helpful to look through all issues in case its already being talked about.
Looking for an idea? Check our issues. If it's look more open ended, it is probably best to post on the issue how you are thinking of resolving the issue so you can get feedback early in the process. We want you to be successful and it can be discouraging to find out a lot of re-work is needed.
Already have an idea? It might be good to first create an issue to propose it so we can make sure we are aligned and lower the risk of having to re-work some of it and the discouragement that goes along with that.
Design guidelines
- Generally grammar-level combinators are free-functions and output/error
conversion are inherent functions on
Parser
.Parser::verify
is an example of some nuance as the logic is coupled to theParser
its applied to. - Combinators that directly process tokens must support complete vs streaming parsing.
- Combinators that process
0..
tokens have a0
suffix,1..
tokens have a1
suffix, and ranged parsers have a_m_n
suffix.
When you first post a PR, we request that the the commit history get cleaned up. We recommend avoiding this during the PR to make it easier to review how feedback was handled. Once the commit is ready, we'll ask you to clean up the commit history. Once you let us know this is done, we can move forward with merging! If you are uncomfortable with these parts of git, let us know and we can help.
For commit messages, we use Conventional
style. If you already wrote your commits and don't feel comfortable changing
them, don't worry and go ahead and create your PR. We'll work with you on the
best route forward. You can check your branch locally with
committed
.
As a heads up, we'll be running your PR through the following gauntlet:
Pre-requisites
- Running
cargo login
- A member of
winnow-rs:Maintainers
- Push permission to the repo
cargo-release
When we're ready to release, a project owner should do the following
- Update the changelog (see
cargo release changes
for ideas) - Determine what the next version is, according to semver
- Run
cargo release -x <level>