-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add Yes + Quit
button to traverse confirmation dialogs
#1607
Conversation
...n/java/com/virtuslab/gitmachete/frontend/actions/dialogs/TraverseStepConfirmationDialog.java
Show resolved
Hide resolved
@@ -353,8 +353,13 @@ class MessageDialogBuilder<T extends MessageDialogBuilder> { | |||
} | |||
|
|||
class MessageUtil { | |||
int showOkCancelDialog(@Tainted String title, @Tainted String message, @Tainted String okText, @Tainted String cancelText, | |||
Icon icon, DoNotAskOption doNotAskOption, Project project); | |||
int showOkCancelDialog(@Tainted String title, @Tainted String message, @Untainted String okText, @Untainted String cancelText, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
while we are here...
I am wondering 🤔 It must happen that sometimes we introduce some stubs and then, after a while modify the code so the stub becomes redundant 🗑️
- For now there is no mechanism to detect unused stubs, right?
- What if we bump IntelliJ version and the stubbed method/class no longer exists? Are there any errors in such case (I do not remember any)? Or is it ignored?
- (assuming 1. is true) Is it a problem the over time we will have more and more redundant stubs? E.g does it significantly affect the compilation/build time? If it is a problem then I might be worth to introduce some detection mechanism.
A bunch of questions 💐 I should have asked them years ago 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It must happen that sometimes we introduce some stubs and then, after a while modify the code so the stub becomes redundant 🗑️
:yes:, it does definitely... still, given the effort that's sometimes needed to figure out these annotations, I'd rather keep these stubs around (even if they might be of little value for the subsequent builds)
- For now there is no mechanism to detect unused stubs, right?
Nope, and I don't think there'll be any. It'd be hard to implement on our side, and I doubt Checker itself will ever support anything like that, given that stubs are kinda redundant by design (i.e. Checker has the entire JDK annotated, even though users will never actually use all of the JDK 😅)
- What if we bump IntelliJ version and the stubbed method/class no longer exists? Are there any errors in such case (I do not remember any)? Or is it ignored?
See https://checkerframework.org/manual/#stub-troubleshooting-type-checking-results... we use -AstubWarnIfNotFoundIgnoresClasses
, so CF reports only missing methods/fields, but ignores missing classes, even if other classes from the same package are present
- (assuming 1. is true) Is it a problem the over time we will have more and more redundant stubs? E.g does it significantly affect the compilation/build time? If it is a problem then I might be worth to introduce some detection mechanism.
I doubt it really affects compilation times... given that Checker Framework itself ships with full annotated JDK!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks! clear!
...n/java/com/virtuslab/gitmachete/frontend/actions/dialogs/TraverseStepConfirmationDialog.java
Show resolved
Hide resolved
df57d99
to
0767f6a
Compare
56da138
to
e285172
Compare
c732926
to
00c4fe0
Compare
@@ -53,6 +53,10 @@ Use IntelliJ IDEA Community Edition/Ultimate. | |||
Set `Class count before import with '*'` and `Names count to use static import with '*'` to a very high number (e.g. 500) | |||
to avoid problems with CheckStyle when editing code, and remove exceptions like `javax.swing.*` from `Packages to Use Import with '*'`. | |||
|
|||
10. (optional) Go to `File > File Properties > Associate with File Type...`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested. works fine 🚀
@@ -283,10 +287,10 @@ Then, update `executors.docker_executor.docker[0].image` in [.circleci/config.ym | |||
|
|||
We follow [Semantic versioning](https://semver.org/) for the plugin releases: | |||
|
|||
* MAJOR version must be bumped for each plugin release that stops supporting any IDEA build (typically when `sinceBuild` is increased). <br/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#1612 for further updates here
df10fbe
to
dfff3e9
Compare
No description provided.