

1·
6 days agoHonestly, that was a good move. JetBrains used to have many actions as popups that prevent reviewing the source code and the project in general while e.g. figuring out a commit message.
🇬🇧 | 24yo French web dev & tech enthusiast
🇫🇷 | Développeur web Limougeaud de 24 ans passionné par l’informatique
Main fediverse account (Mastodon) : mamot.fr/@KaKi87
Blog (Lemmy) : blog.kaki87.net
Formerly @KaKi87@sh.itjust.works, moved because of Cloudflare.


Honestly, that was a good move. JetBrains used to have many actions as popups that prevent reviewing the source code and the project in general while e.g. figuring out a commit message.
Yes, but only the diff.
What if my change is one parameter in a function call ? The most meaningful aspect of the change lies in the definition of said function, that may not be part of the diff.
What if my change is related to another commit that I want to reference in my message ? I’d have to close the dialog, copy the commit ID, and reopen the dialog.
For an infinite amount of reasons we rarely foresee, blocking states are never good.
Same.
But this one thing isn’t part of said shitty design.