HTL: Add support for "/libs/granite/sightly/templates/clientlib.html"

[deeprim]

"/libs/granite/sightly/templates/clientlib.html" template should be proposed as data-sly-use option.

Once it selected in data-sly-use, it should be proposed in data-sly-call:

• js
• css
• all

Once it selected in data-sly-call, corresponding "Template Arguments" should be proposed in data-sly-call options:

• categories

For categories option clientlibs available in the project should be proposed as completion variants

• Add /libs/granite/sighlty/templates/clientlib.html for data-sly-use completion
• Add index for all clientlibs in the project
• data-sly-call for clientlib.html should have completion for js & css
• "Options" completion for either js or css should have categories as "top" variant
• Completion for categories option should have all clientlibs available in project (clientlibs that have "embed" attribute should go first)
• Quick doc action should be available for categories value (e.g. categories='<caret>my-cat'). The documentation should reveal all data regarding selected category

[dmitry-cherkas]

I guess, it would be a better option to index all OOTB AEM templates and use this index for auto-suggest.

[deeprim]

Hi @dmitry-cherkas ,

Though, the indexing of OOTB AEM templates sounds like a good feature.
The specific semantics (the clientlibs template should be called with client libs, the category) could not be indexed, i.e. required to be implemented anyway

[deeprim]

The completion is broken, reopened

[koha26]

@deeprim
I fixed documentation in scope of #205. In addition, I added documentation for categories, embeds, dependencies in the clientlibs folder.

Also, completion has been fixed in 07768bf commit.
Now, all items from the list in the description work as expected.