It's always a good idea to work on documentation. There are a few open issues labeled with 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)
• Move "Instal

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

Summary

Some fields like:

• displayedAttributes in GET /index/:uid:/settings and GET /index/:uid:/settings/displayed-attributes routes
• facetsDistribution in a search query /indexes/test/search?facetsDistribution=%5B%22color%22%5D

are never consitently sorted between same requests.

Motivations

Same request should respond same results in the same order.

Implementa

Describe the bug
I was opening the main .toml file in the project root when I discovered this. Using the command:

open Cargo.toml | get bin | get required-features, produces both an output table, and an error:

> open Cargo.toml | get bin | get required-features
────┬────────────
  0 │ textview   
  1 │ inc        
  2 │ ps         
  3 │ sys        
  4 │ fetch     

The image crate with default options is the absolute leader in code size:

 File  .text     Size Crate
 5.7%  14.6% 364.0KiB image
 4.6%  12.0% 297.3KiB wgpu_native
 3.8%   9.9% 246.5KiB std
 3.5%   8.9% 222.1KiB usvg
 2.6%   6.8% 170.0KiB iced_wgpu

I don't need to support ico, bmp, tga, hdr, dxt, dds, farbfeld and so on in a program that would only ever decode

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
I'd like the source code to be automatically clang-formatted according to my settings anytime the code is compiled. That is, don't require me to use the contextual menu or keyboard shortcut to format the code. Just auto-format it; just like the code is auto-compiled too.

Well, ther

Add a field on the breakpoint that shows the number of times a breakpoint was hit. See The -break-list Command.

it would be good to have
min-width, max-width <-- this 2 is good for PWA, if user resized it too small, it would become ugly.
maximized <-- this would be maximized on first load.

another thing would be, try delay webview resize when the host window resize, like how all the browser did, this would make sure PWA reflective size won't response immediately... current resize is seriously lagging

It would be neat if you could change the color of the text that shows when the progress bar covers it without changing the background. My motivation is that I enjoy the black background but the default color can be hard to read on dark progress bar colors.

<img width="1423" alt="Screen Shot 2020-06-06 at 11 50 41 AM" src="https://user-images.githubusercontent.com/16331012/83952212-14b8d780-