Skip to content
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

Soften the warning around cider-nrepl version mismatches #3064

Closed
wants to merge 1 commit into from

Conversation

vemv
Copy link
Member

@vemv vemv commented Oct 5, 2021

Especially given we try to inflict as few breaking changes as possible (#2960), a version mismatch might simply mean that one is using a more recent cider-nrepl version (without one having bothered to customize the related defcustom to silence this).

This commit proposes a softer wording for the warning, so that people feel less alarmed in face of these.

Else one gives the quite untruthful impression that things are more fragile/coupled than they actually are.

Especially given we try to inflict as few breaking changes as possible (#2960),
a version mismatch might simply mean that one is using a more recent cider-nrepl version (without one having bothered to customize the related `defcustom` to silence this).

This commit proposes a softer wording for the warning, so that people feel less alarmed in face of these.

Else one gives the quite untruthful impression that things are more fragile/coupled than they actually are.
@bbatsov
Copy link
Member

bbatsov commented Oct 5, 2021

I like the current message more, as it's both short, informative and neutral. Once we get to the point of a really stable API we might not show any warning for newer cider-nREPL at all, but I don't think that we're quite there yet. At the very least we have to get to a 1.0 release soon.

It might be a good idea to add a way to suppress those messages for users who really know what they are doing. Still, my observation is that almost no one outside of the people hacking on CIDER changes those versions, so such a configuration option might be an overkill.

Btw, we never use terms like cider.el in the messages - it's always CIDER everywhere.

@vemv vemv marked this pull request as draft October 18, 2021 13:56
@vemv vemv closed this Nov 5, 2021
@vemv vemv deleted the soften-warning branch August 27, 2023 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants