Provide a preference page

[fbricon]

Those settings should be exposed in a preference page:

Quarkus

• quarkus.tools.debug.terminateProcessOnExit : Determines whether to terminate the quarkus:dev task after closing the debug session. Default is Ask.
• quarkus.tools.alwaysShowWelcomePage : Determines whether to show the welcome page on extension startup. Default is true.
• quarkus.tools.starter.api : Quarkus API base URL. Default is https://code.quarkus.io/api.
• quarkus.tools.starter.showExtensionDescriptions: Determines whether to show the Quarkus extension descriptions when selecting Quarkus extensions. Default is true.
• quarkus.tools.propertiesLanguageMismatch : Action performed when detected Quarkus properties have an incorrect language. Default is forceQuarkus.

Microprofile

• microprofile.tools.formatting.surroundEqualsWithSpaces : Insert spaces around the equals sign when formatting the application.properties file. Default is false.
• microprofile.tools.trace.server : Trace the communication between VS Code and the MicroProfile Language Server in the Output view.
• microprofile.tools.symbols.showAsTree : Show MicroProfile properties as tree (Outline). Default is true.
• microprofile.tools.validation.enabled : Enables MicroProfile validation. Default is true.
• microprofile.tools.validation.duplicate.severity : Validation severity for duplicate properties for MicroProfile *.properties files. Default is warning.
• microprofile.tools.validation.syntax.severity : Validation severity for property syntax checking for MicroProfile *.properties files. Default is error.
• microprofile.tools.validation.required.severity : Validation severity for required properties for MicroProfile *.properties files. Default is none.
• microprofile.tools.validation.expression.severity : Validation severity for property expressions for MicroProfile *.properties files. Default is error.
• microprofile.tools.validation.unknown.severity : Validation severity for unknown properties for MicroProfile *.properties files. Default is warning.
• microprofile.tools.validation.unknown.excluded : Array of properties to ignore for unknown properties validation. Patterns can be used ('*' = any string, '?' = any character). Default is ["*/mp-rest/providers/*/priority", "mp.openapi.schema.*", "kafka-streams.*", "camel.*"].
• microprofile.tools.codeLens.urlCodeLensEnabled : Enable/disable the URL code lenses for REST services. Default istrue.
• microprofile.tools.validation.value.severity: Validation severity for property values for MicroProfile *.properties files. Default is error.
• microprofile.tools.validation.unassigned.excluded: Array of properties to ignore for unassigned properties validation in Java files. Patterns can be used ('*' = any string, '?' = any character).

Qute

• qute.server.vmargs: Set the arguments to pass to the JVM while launching qute-ls. Default is -Xmx100M -XX:+UseG1GC -XX:+UseStringDeduplication -Xlog:disable

• qute.trace.server: Trace the communication between VS Code and the Qute language server in the Output view. Default is off.

  • qute.native.enabled: Enable/disable Qute validation/completion for native image mode. Default is false.
  • qute.codeLens.enabled: Enable/disable Qute CodeLens. Default is true.
  • qute.inlayHint.enabled: Enable/disable Inlay Hint. Default is true.
  • qute.inlayHint.showSectionParameterType: Show section parameter type. Default is true.
  • qute.inlayHint.showMethodParameterType: Show method parameter type. Default is true.
  • qute.validation.enabled: Enable/disable all Qute validation. Default is false.
  • qute.validation.excluded: Disable Qute validation for the given file name patterns.

  Example:

  [
   "**/*items.qute.*"
  ]

  • qute.validation.undefinedObject.severity: Validation severity for undefined object in Qute template files. Default is warning.
  • qute.validation.undefinedNamespace.severity: Validation severity for undefined namespace in Qute template files. Default is warning.

[angelozerr]

I think we should have thoses preferences pages:

• Language Servers which show in a list the available language server as master. When we click on a language server we could have a detail which show debug port for instance to debug it.
• Microprofile
  • Quarkus
    • Qute