-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simpler API for configuring simple rules #580
Labels
Comments
jmfayard
added a commit
that referenced
this issue
Sep 5, 2022
This was referenced Sep 5, 2022
jmfayard
added
not-for-this-release
core feature
needs-feedback
not enough feedback to start working on this
and removed
not-for-this-release
labels
Sep 6, 2022
Wouldn't this be obsolete with version references support in versions catalogs? |
No, not for |
One thing that #211 reminded me is that once we have that, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I opened a small PR to demo how we could simplify configuring the rules
#581
My vue (stolen from the Perl community) is that:
Rules files do the second half right, the first half not so much.
We have issues like #575 that show people would like for a way to avoid/simplify need for rules files.
I did a GitHub code search on
refreshVerisons.extraArtifactVersionKeyRules
see here and only 4 people have configured one during the last month.If you look at the rules we have, some are powerful like in
AndroidX
but most rules are super simple and could be modeled this way:That would not change anything fundamental for refreshVersions, the
PrefixRule
would simply be converted to a rules file in the background.(I started to write this code already, it works)
Things to consider
The text was updated successfully, but these errors were encountered: