Opening a .class file on a remote window doesn't show decompiled source

[apimentasoto]

The custom editor for java class files is not used when opening .class files on a remote window.

I use the remote development extension for WSL.

The glob used as selector for the editor won't match the scheme of remote files.

"selector": [
          {
            "filenamePattern": "file:/**/*.class"
          }
]

Got it working adding a pattern which matches remote files:

"selector": [
                    {
                        "filenamePattern": "file:/**/*.class"
                    },
                    {
                        "filenamePattern": "vscode-remote:/**/*.class"
                    }
]

I'm new to remote development so I have no idea if I should be seeing this scheme in the first place. In any case would be nice to have .class files open the decompiled source by default - currently there is no error message or any indication that something's missing - just the 'cannot open binary file' page.

[nkilders]

I was facing the same problem, but don't completely understand your solution. What's the full name of the setting you use? Here is an alternative solution which works for me. Both patterns seem to be fine.

{
	"workbench.editorAssociations": {
		"*.class": "decompiled.javaClass",
		// or
		"vscode-remote:/**/*.class": "decompiled.javaClass",
	},
	...
}

Edit: the *.class pattern causes problems when using Ctrl+click to jump into class files. It does not focus the correct line (e.g. of the method you clicked), but always the beginning of the file. The other pattern works without this problem.

[apimentasoto]

Oh I was refering to the selectors configured by the extension when the editor is contributed. Changing those would make the editor open class files on remote windows out of the box.
Here

I didn't even think about using user settings to fix this but it makes a lot of sense if the package.json of the extension is not updated.

[nkilders]

Ahh, now I get it. Yes, your solution would be much better, as it would work without any configuration effort on the user's side. I have created a PR which adds the new filename pattern to the package.json file. Let's see what happens 😊