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

Enhance Jar Reload Functionality for Improved Workflow #630

Closed
EricKrohnfeldt opened this issue Jan 31, 2024 · 5 comments
Closed

Enhance Jar Reload Functionality for Improved Workflow #630

EricKrohnfeldt opened this issue Jan 31, 2024 · 5 comments

Comments

@EricKrohnfeldt
Copy link

Description:
Currently, when building a new version of the JAR with custom checks, the process of reloading the JAR involves navigating to settings and either editing or deleting and re-adding the third-party check row. This workflow is cumbersome and could be streamlined for better efficiency.

Request:
Use "Reload" button to easily refresh or reload the JAR without the need to manually edit or delete and re-add the third-party check row. This enhancement would greatly improve the user experience and save time during the development process.

image

@jshiell
Copy link
Owner

jshiell commented Feb 4, 2024

Seems a very fair request, and I'm surprised it doesn't do it already. I think it's fairly simple, but will require a little refactoring to remove the (partial) dup of the code here; I'm out of time to work on this today but will try have a look next weekend.

jshiell added a commit that referenced this issue Feb 4, 2024
@jshiell
Copy link
Owner

jshiell commented Feb 4, 2024

Code is pushed, but testing is cursory at best so I'm not prepared to release it just yet.

@jshiell
Copy link
Owner

jshiell commented Feb 11, 2024

It's not looking like I'll get much time to look at it this weekend, but here's a link to a test build, in case that's of use.

@EricKrohnfeldt
Copy link
Author

No rush. I just reel better knowing it's in the pipe.

@jshiell
Copy link
Owner

jshiell commented Feb 18, 2024

Hopefully fixed in 5.87.1 - if it doesn't work for your use case, please reopen, and I'll take another go (experience has taught me never to be overconfident regarding anything involving caching).

@jshiell jshiell closed this as completed Feb 18, 2024
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

No branches or pull requests

2 participants