No default (unnamed) suggestions on properties that can be named

[gian1200]

Following on from #734 (comment).

Some properties support named and unnamed references (e.g. datasource). This means that all it's properties it can be defined once and there is no need to include a name (default). However, it's also possible to have multiple instances of the same "type", and adding a name is used to identify how properties are grouped/assigned.

These properties usually comes in the form `quarkus.xxx.{*}.xxx´, where xxx can be a single or multiple levels. Example:

quarkus.datasource.db-kind=h2
quarkus.datasource.username=username-default
quarkus.datasource.jdbc.url=jdbc:h2:mem:default
quarkus.datasource.jdbc.max-size=13

quarkus.datasource.users.db-kind=h2
quarkus.datasource.users.username=username1
quarkus.datasource.users.jdbc.url=jdbc:h2:mem:users
quarkus.datasource.users.jdbc.max-size=11

quarkus.datasource.inventory.db-kind=h2
quarkus.datasource.inventory.username=username2
quarkus.datasource.inventory.jdbc.url=jdbc:h2:mem:inventory
quarkus.datasource.inventory.jdbc.max-size=12

Taken from https://es.quarkus.io/guides/datasource#configure-multiple-datasources

Escenario:

From the following example, I expected to also have quarkus.datasource.db-kind and quarkus.datasource.db-version as a suggestions (before the other suggestions).

[angelozerr]

I wonder if some properties must define this name? If yes, how to detect that?

My first feeling is that those name are optional (@gmset am I right?)

In this case , my suggestion is when completion is applied, we remove this named (*} to generate quarkus.datasource.db-kind instead of quarkus.datasource.name.db-kind like today.

After that when completion is reopened (quarkus.datasource.db-kind exists in the properties file), when completion is applied it generates quarkus.datasource.name.db-kind

@gian1200 what do you think about this idea?