Currently we implement our own data url parsing in the data_url_media_type function in the lsp: https://github.com/denoland/deno/blob/1ed95120225eb3d7c9adeadcc3b1f610dbe55b7e/cli/lsp/urls.rs#L52-L61

We also implement a slightly different parser in the module loader: https://github.com/denoland/deno/blob/8d55d8b6be8731d37ccf6a29127b3a91a8319d0b/cli/file_fetcher.rs#L156-L188

Both of these cu

It's always a good idea to work on documentation. I think it would also be good to restructure the README:

• Add a quick link section at the top of the readme (see https://github.com/sharkdp/bat)
• Extend the tutorial (rename "How to use"?)
• Move the "Parallel command execution" section inside the "How to use" section). See also: #605
• Move "Installation" section below the

The documentation contains a few references to issues from the now archived yewstack/docs repository.
Since the docs repository is read-only, the same issues should be re-created here and the links in the docs should be updated to point to the new issue.

"Contribute to our docs" links

• Page: [Components Lifecycle Diagram](https://yew.rs/docs/conce

Describe the solution you'd like
It'd be nice to actually apply the security framework when building.

Describe alternatives you've considered
Ignoring security problems won't help.

Describe the bug
The open command uses the bat crate to nicely render text files.
The docs here: https://www.nushell.sh/book/configuration.html#nushell-configuration-with-config-toml
say that setting the [textview] vcs_modification_markers option to true causes it to show modification markers, but it doesn't currently work. However, running bat on the same file does show modific

Right now any StyleSheet has a list of functions without a default implementation. Implementing a StyleSheet is really annoying, because you have to override all of the functions and not just the thing you want to change.

I recently wanted to just change the border_radius of a text_input and I had to write the following code.

impl StyleSheet for Styles {
    fn active(&self) ->

Currently, with dark theme only available colour scheme is grey shades, while light mode offers multiple colour schemes. With only greys, it can be hard to tell difference between shades.

It might be good idea to add (more) colour schemes to dark mode. Even just copying schemes from light mode would be a good start, although they might need a bit of tweaking to avoid heavy contrast with backgro

What problem does this solve or what need does it fill?

Selecting particular camera types is frustrating, relying on checking the name field within a system.

What solution would you like?

Add a simple marker components for UiCamera and GameplayCamera.

What alternative(s) have you considered?

Users can add their own marker components manually.

Only tag UiCamera and