-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
[BREAKING] Move 3rd-party
appenders to community
#322
Comments
ptaoussanis
added a commit
that referenced
this issue
Mar 22, 2022
ptaoussanis
added a commit
that referenced
this issue
Mar 22, 2022
ptaoussanis
added a commit
that referenced
this issue
Mar 22, 2022
ptaoussanis
added a commit
that referenced
this issue
Mar 22, 2022
ptaoussanis
added a commit
that referenced
this issue
Jul 7, 2022
Marking as done, will be included in forthcoming release 👍 |
ptaoussanis
added a commit
that referenced
this issue
Oct 19, 2022
ptaoussanis
added a commit
that referenced
this issue
Oct 20, 2022
ptaoussanis
added a commit
that referenced
this issue
Oct 20, 2022
ptaoussanis
added a commit
that referenced
this issue
Oct 23, 2022
Before this commit: Community appender namespaces: `taoensso.timbre.appenders.3rd-party.X` After this commit: Community appender namespaces: `taoensso.timbre.appenders.community.X`. This is a BREAKING change for you iff: You're using any of the included community appenders. In this case, just change `3rd-party` in your ns imports to `community`. Motivation for change: The `3rd-party` namespace segment beginning with a numeric has long caused minor issues with tooling, etc. (e.g. #322). Took the opportunity to also exclude community code from the default Lein profiles to help prevent community code with strange dependencies and/or environment expectations (e.g. Android platform) from interfering with builds, cljdoc, etc.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like ClojureScript doesn't like namespace segments starting with a digit. Might be time to move everything under a
community
namespace?The text was updated successfully, but these errors were encountered: