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

Add way to disable run and debug buttons on main function definition. #464

Closed
ThadHouse opened this issue Oct 27, 2018 · 3 comments
Closed
Milestone

Comments

@ThadHouse
Copy link
Contributor

I have a build where if you just attempt to run the main function, it fails to start, because I have some native dependencies that need to be configured. I am providing this build to a large amount of users, and it is confusing our users, as those buttons do not work, and they throw very confusing errors. Could a property be added to disable these buttons from showing up?

ThadHouse added a commit to ThadHouse/vscode-java-debug that referenced this issue Oct 31, 2018
There are cases where it will never work properly, and it is confusing a chunk of my users that attempt to use it, and wonder why it fails

Closes microsoft#464
ThadHouse added a commit to ThadHouse/vscode-java-debug that referenced this issue Oct 31, 2018
There are cases where it will never work properly, and it is confusing a chunk of my users that attempt to use it, and wonder why it fails

Closes microsoft#464
ThadHouse added a commit to ThadHouse/vscode-java-debug that referenced this issue Oct 31, 2018
There are cases where it will never work properly, and it is confusing a chunk of my users that attempt to use it, and wonder why it fails

Closes microsoft#464
testforstephen pushed a commit that referenced this issue Oct 31, 2018
* Add way to disable run and debug code lens provider

There are cases where it will never work properly, and it is confusing a chunk of my users that attempt to use it, and wonder why it fails

Closes #464

* Add translation support

* Add type to lambda

* Add period to description
@ThadHouse
Copy link
Contributor Author

Quick question maybe @testforstephen

Is there an estimated release cadence for this repo? I can't find one, and this bug at least for me is a blocker that would be really nice to have fixed by sometime in mid November at the latest. Is that possible?

@andxu
Copy link
Contributor

andxu commented Oct 31, 2018

We will release it tomorrow.

@andxu andxu added this to the 0.15.0 milestone Oct 31, 2018
@sallyur sallyur mentioned this issue Nov 1, 2018
8 tasks
@andxu
Copy link
Contributor

andxu commented Nov 1, 2018

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