Completion should propose all leaf variables?

[smedilol]

With this kind of syntax:

       01 Person typedef strict.
         03 Names.
           05 LastName  pic X(30).
           05 FirstName pic X(30).
         03 BirthDate type Date.
      01 Person1 type Person.

When you ask for completion after: move Person1:: you only get:

Names
BirthDate

Shouldn't it be better to have all leaf variables as well?

Names
Names::LastName
Names::FirstName
BirthDate

So someone who don't know the structure doesn't have to look at its definition.

[smedilol]

This mechanism is already implemented when you ask completion for a procedure parameter.

[collarbe]

It's slightly different between procedure parameter completion and QualifiedName completion.

The pros of getting leaf children on QualifiedName completion is the fact that the developer will get the final variable quickly.

The cons of that is the fact that if there is a lot of children the completion list could be very extensive. Also, do we stop completion to propose only the first children or do we suggest all the available paths until the last children

You can discuss about that later :)

[maxime645]

There should be an option client side enable or disable this functionnality and let the programmer decide if he wants to use it or not.