Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd setting to enable asserts. #876
Comments
|
What's asserts? Please explain your user scenario with more details. |
|
assert is a keyword in Java, and it behaves like assert does in c++. https://docs.oracle.com/javase/7/docs/technotes/guides/language/assert.html They can be enabled normally by adding a flag to java at runtime. They are not enabled by default when debugging using the vscode extension. |
|
Thanks for the details. Currently you can add vmArgs to "-ea" in the launch.json to enable assert. In future, we're planning to expose a global vmArgs in the user settings, where you can add "-ea" as the default value. |
|
I currently don't have a launch.json. Should I be expecting one to be present? |
|
By default, the debugger just generates the config in memory. But you could go the debug view to create a launch.json.
|
|
With the latest debugger, you could achieve this by adding user setting |
Currently when I run the debugger, my asserts are not being triggered.
It would be nice if there was a way I could turn on asserts, potentially in an extension setting or something.