You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
It would be nice if the custom extensions configured in "File Types" could be exempted from this behaviour.
The text was updated successfully, but these errors were encountered: