Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurations from files included with extensions other than .conf are not part of string auto-suggestion #29

Open
sivaraam opened this issue Aug 27, 2020 · 0 comments

Comments

@sivaraam
Copy link

The auto-suggestion in Java strings works well when I have a application.conf with configurations. Including files with a .conf extension also work fine. But when I include a file with a different extension the configurations in those files don't show up in the auto-completion. This is a drawback for as our project maintains the HOCON configurations in files with a custom extension (let's say .mf).

Adding the custom extension to File -> Settings -> Editor -> File Types doesn't work either. To be clear: the highlighting, Find usages, etc. work fine. But the setting doesn't seem to have any effect on the includes.

I went through #24 and it looks like the reason is as mentioned in the following comment:

Yes, it makes sense, but it will also require changing semantics of includes so that include "foo" could be interpreted as include "foo.hocon" (and that include "foo.hocon" is not interpreted as include "foo.hocon.conf").

It would be nice if the custom extensions configured in "File Types" could be exempted from this behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant