-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fix clj-kondo warnings #32
Comments
Update: @rschmukler mentioned that running |
Seems clearing the cache as mentioned above is indeed successful, so closing this issue. |
@icp1994 To confirm, you tried to first run |
Yes. I also started a fresh dummy project to make sure. |
I'm not familiar with clj-kondo myself so unfortunately can't advise - but hopefully someone else might be able to. @rschmukler Is there anything else you can suggest for @icp1994 to try? Thanks! 🙏 (Tagging you because of your comment on the Telemere Slack). |
I think there needs to be separate config which users can import, like there is for nippy. |
I'm hoping that might not be the case, since it seems there's at least two clj-kondo users here that have reported success after clearing their cache. Not sure though! Hopefully someone else familiar with clj-kondo can advise? |
Currently, it looks like clj-kondo generates spurious warnings for Telemere (Ref. Slack):
I'm not familiar with with clj-kondo, but as I understand it - Telemere could help get rid of these warnings by including some sort of relevant data file.
This'd be a good first PR if someone familiar with clj-kondo wants to help out. Feel free to ping if I can provide any assistance re: relevant signatures / arg types / etc.
In the meantime, my understanding is that the following config will suppress the spurious warnings (Ref. Slack):
The text was updated successfully, but these errors were encountered: