Hello everybody, you'll be happy to know that in the next version of komorebi (v0.1.19), a complete refactor of matching rules will be shipped. 🎉
Each identifier object will now take an optional matching_strategy, which if not set, will default to Legacy in order to avoid breaking changes for existing users.
These will be available to use both here in applications.yaml, and in your own personal komorebi.json files.
If you would like to contribute to the komorebi ecosystem, this issue is a great place to start! You can work on PRs adding simple matching strategies like Equals for exes, or more complex rules using regexes which have not been possible to build until now.
We will hold off on merging any of these PRs until v0.1.19 has been out for a week or so to give people time to upgrade, so don't worry if you don't see your PRs merged immediately!
Hello everybody, you'll be happy to know that in the next version of
komorebi(v0.1.19), a complete refactor of matching rules will be shipped. 🎉Each
identifierobject will now take an optionalmatching_strategy, which if not set, will default toLegacyin order to avoid breaking changes for existing users.The
matching_strategyoptions available will be:Legacy- Whatkomorebihas done until nowStartsWith- stdlib functionEndsWith- stdlib functionContains- stdlib functionEquals- stdlib functionRegex- Any regex that can be compiled by the default settings/features of theregexcrateThese will be available to use both here in
applications.yaml, and in your own personalkomorebi.jsonfiles.If you would like to contribute to the
komorebiecosystem, this issue is a great place to start! You can work on PRs adding simple matching strategies likeEqualsfor exes, or more complex rules using regexes which have not been possible to build until now.We will hold off on merging any of these PRs until v0.1.19 has been out for a week or so to give people time to upgrade, so don't worry if you don't see your PRs merged immediately!