File Associations don't work when file only have extension(_no filename_)

[parallels999]

Apache NetBeans version

Apache NetBeans 21

What happened

On php laravel there is .env file, without name, only extension
https://github.com/laravel/laravel/blob/58baff2c70144c7cd4c04eecb51fee5a24e873a8/composer.json#L42
After adding File Association, works on any *.env file, except for the one that has no name, only extension(main one)

Language / Project Type / NetBeans Component

PHP project

How to reproduce

Just create any file with new extension but without name, only the extension, add the File Association(I'm using text/x-apache-conf), then File Association does't work on that file

Did this work correctly in an earlier version?

No / Don't know

Operating System

Windows

JDK

11

Apache NetBeans packaging

Apache NetBeans provided installer

Anything else

No response

Are you willing to submit a pull request?

No

[matthiasblaesing]

This is not a bug, but works as intended (lines 232 + 239):

netbeans/platform/masterfs/src/org/netbeans/modules/masterfs/filebasedfs/utils/FileInfo.java

Lines 229 to 241 in 905ff7e

	public static final String getName(String name) {
	int i = name.lastIndexOf('.');
	/** period at first position is not considered as extension-separator */
	return (i <= 0 || i == (name.length()-1)) ? name : name.substring(0, i);
	}
	public static final String getExt(String name) {
	int i = name.lastIndexOf('.') + 1;
	/** period at first position is not considered as extension-separator */
	return ((i <= 1) || (i == name.length())) ? "" : name.substring(i); // NOI18N
	}

With my linux hat on, I agree with that assessment. Traditionally files with leading dot are hidden files. So from that perspective .env is not a file that has only an extension, but a hidden file, that has no extension.

[parallels999]

So from that perspective .env is not a file that has only an extension, but a hidden file, that has no extension.

Yes, on linux, but windows is another story, right?

[Chris2011]

In the world of DOT files inside of the projects nowadays (.eslintrc, .prettierrc, .env, .anything) we should handle them too. It is not just a linux/windows thing anymore I would say. Let this convert to a discussion to talk about the cases.

[cesarreyes3]

On DOT files are really hard comment/uncomment code blocks, You have to do it line by line depending on the mimetype

[fredsal]

Other editors open DOT files with correct highlighting

[matthiasblaesing]

Sure and NetBeans could do so too, if people would implement it. The Apache conf example might be very helpful for this.

1. Define the way your mimetype is detected:

   netbeans/webcommon/languages.apacheconf/src/org/netbeans/modules/languages/apacheconf/resources/ApacheConfResolver.xml

   Lines 29 to 32 in ecc3f23

   	<file>
   	<name name=".htaccess" />
   	<resolver mime="text/x-apache-conf"/>
   	</file>

2. Register it in the IDE:

   netbeans/webcommon/languages.apacheconf/src/org/netbeans/modules/languages/apacheconf/ApacheConfDataObject.java

   Lines 43 to 47 in ecc3f23

   	@MIMEResolver.Registration(
   	displayName="#ApacheConfResolver",
   	position=131,
   	resource="resources/ApacheConfResolver.xml"
   	)

Registering by name might be exposed in GUI, but that needs work and someone championing the effort.