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?

Agree, we need a setting

What about xml.completion.fileSupport.enabled?

@AlexXuChen are you interested to work on this issue?

Thanks for your quick support guys, great extension!

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

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

@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 .

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)

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

@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.

@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?

Trace.log

Here you are...

Hi guys, any news about this issue?

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

@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.