fix: missing asset protocol path

[wusyong]

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Docs
• New Binding Issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes. Issue #___
• No

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[wusyong]

Let me do some final check to see if it's not required on mac/linux

[ArturKovacs]

Is it true that the application code will have to produce asset://localhost/path/to/file on Windows but it must produce asset://path/to/file on every other system? If this is true what's the reasoning behind this distinction?

It seems simpler to just have to specify asset://path/to/file on every platform.

[lucasfernog]

Windows doesn't support custom protocols yet (such as asset://). That's why we have a convertFileSrc helper API.

[ArturKovacs]

Sorry I may have been confused about how this should be used. So if I understand it correctly my javascript should look something like this:

let video = new HTMLVideoElement();
video.src = convertFileSrc("C:/path/to/my video.mp4");

[wusyong]

@ArturKovacs yes.
Btw we are looking into ways for streaming data. So you won't have to get entire binary for the video.

[ArturKovacs]

Sounds great, thank you!