feat: register-local-version protocol command

[samuelmaddock]

Implements protocol handler for electron-fiddle://register-local-version/ to allow registering local versions.

Example request:

electron-fiddle://register-local-version/?name=feat%3A+service+worker+preload+scripts&version=35.0.0-dist&path=%2FUsers%2Fsamuelmaddock%2F.electron_build_tools%2Fartifacts%2Fpr_44411_darwin_arm64

This is intended to be used by build-tools as a way to quickly download build artifacts and test them in Fiddle.

Screen.Recording.2024-11-21.at.7.24.22.PM.mov

[coveralls]

coverage: 87.628% (+0.02%) from 87.604%
when pulling ec0aa34 on samuelmaddock:feat/register-local-version
into 3452e12 on electron:main.

[erickzhao]

This is a really elegant implementation!

[dsanders11]

This should have a confirmation dialog similar to the one we show when we load Fiddles from the docs.

fiddle/src/renderer/remote-loader.ts

Lines 251 to 261 in 3452e12

	/**
	* Verifies from the user that we should be loading this fiddle.
	*
	* @param what - What are we loading from (gist, example, etc.)
	*/
	public verifyRemoteLoad(what: string): Promise<boolean> {
	return this.appState.showConfirmDialog({
	label: `Are you sure you want to load this ${what}? Only load and run it if you trust the source.`,
	ok: 'Load',
	});
	}

I'm also a bit weary from a security perspective to expose modifying Fiddle's list of local builds like this. I think it warrants stronger consideration of how it might be abused.

[samuelmaddock]

@dsanders11 I've added a confirmation dialog. While testing I noticed that multiple requests will clobber the previous dialog. I've gone ahead and added a fix for that as well.

Screen.Recording.2024-11-22.at.7.15.33.PM.mov

[MarshallOfSound]

This shouldn't be a protocol URL that can in theory be triggered by remote pages, make it a CLI argument to the fiddle binary instead and have build tools spawn fiddle, trigger the second instance event and handle that.

Also fiddle that confirm with the user they actually want to register this thing before it just Does What It Was Told

[samuelmaddock]

This shouldn't be a protocol URL that can in theory be triggered by remote pages, make it a CLI argument to the fiddle binary instead and have build tools spawn fiddle, trigger the second instance event and handle that.

I feel like this gets exceedingly difficult when there are multiple installations or apps installed outside of the default directory (especially on Windows).

Also fiddle that confirm with the user they actually want to register this thing before it just Does What It Was Told

Added in the most recent commit.