Validate application.properties: required properties

[angelozerr]

Validate application.properties:

• required Quarkus properties. See case 1 in https://quarkus.io/guides/application-configuration-guide#injecting-configuration-value.

[xorye]

@angelozerr is this issue only for @ConfigProperty?

If this issue is also for @configroot, @configitem etc, I will investigate more about the meaning of "required" for @configroot, @configitem etc.

[angelozerr]

The original issue was about required for any annotation but we can split this issue in two issues if you wish. Please rename this issue (by adding for ConfigProperty) and create a new issue for ConfigRoot.

But it means ExtendedConfigDescriptionBuildItem should return the annotation origin of the Quarkus property computing,no?

[xorye]

But it means ExtendedConfigDescriptionBuildItem should return the annotation origin of the Quarkus property computing,no?

Can this be inferred from location or source?

quarkus-ls/quarkus.ls/com.redhat.quarkus.ls/src/main/java/com/redhat/quarkus/commons/ExtendedConfigDescriptionBuildItem.java

Lines 37 to 38 in 9ddc40b

	private String location;
	private String source;

[angelozerr]

No, you can have ConfigRoot and ConfigProperty from JARs and source both. If you wish I can manage that in an another PR. For the moment you could check if property starts with quarkus (=ConfigRoot).

[xorye]

Maybe it might be better to depend on required, since it would take care of required for any annotation. I will investigate more

[angelozerr]

Maybe it might be better to depend on required, since it would take care of required for any annotation. I will investigate more

Yes it was my idea. You need to fill th erequired info from the JDTQuarkusManager. If you need help, please tell me

[angelozerr]

Fixed with #91