Unwanted autocompletion

[DaWolfi]

Every time I start typing in an empty string or at the end of a string, an autocompletion window opens with filenames of the directory, which contains the file in use:

If I disable the XML extension this autocompletion doesn't show up any more.

Can anybody please help me to disable this "feature"!

Version: 1.65.0-insider (user setup)

[angelozerr]

Its not possible to disable it. We need to provide a settings for that like xml.completion.fileSupport

@fbricon what do you think about that?

[fbricon]

Agree, we need a setting

[angelozerr]

What about xml.completion.fileSupport.enabled?

@AlexXuChen are you interested to work on this issue?

[DaWolfi]

Thanks for your quick support guys, great extension!

[AlexXuChen]

@fbricon What should the default behaviour be for this setting?

[fbricon]

I'd say it could support boolean (true by default) and file glob patterns.

[fbricon]

@DaWolfi I don't understand how you get file name completion though, from your picture. It should only kick in if you start the attribute value with / or \ or .

[angelozerr]

Instead of having only glob patterns I think we should have xpath too exactly like we have for symbole filters.

All mechanism already exists (perhaps with some refactoring)

[angelozerr]

With xpath I mean we could write @path to allow file completion for path attribute

[DaWolfi]

@DaWolfi I don't understand how you get file name completion though, from your picture. It should only kick in if you start the attribute value with / or \ or .

@fbricon : I also thought that it should work this way, because I used a path autocompletion extension before. But even though I disabled all other extensions, the result is always the same.

[fbricon]

@DaWolfi can you set the "xml.trace.server" preference to "verbose" and give us the logs from the "XML Support" Output channel, from startup to file name completion?

[DaWolfi]

Trace.log

Here you are...

[DaWolfi]

Hi guys, any news about this issue?

[angelozerr]

No sorry we had.no time to work on that. I know this completion file feature is annoting for camel //cc @apupier

We need to filter this file completion with a new completion file filtrer wherr we can write some xpath like we have with symbol filter. We could define a default value to allow some attributs like @path @file

[datho7561]

@DaWolfi I don't understand how you get file name completion though, from your picture. It should only kick in if you start the attribute value with / or \ or .

If you manually trigger completion in an attribute value that has non-empty content, file names are suggested for completion. None of these suggestions work, since the completion item doesn't replace the text you've already entered. I'll look into addressing two things

• Don't suggest path names unless the string starts with a / or a ./ or a [A-Z]:\\ or a .\\
• Make sure the path autocompletions replace the entire attribute value when you accept them

Instead of having only glob patterns I think we should have xpath too exactly like we have for symbole filters.

I honestly don't think this is worth the while if all we need to do is fix the existing behaviour of path completion suggestions.