Viacheslav Turovskyi

@derberg Fixed.

**Following [https://github.com/asyncapi/asyncapi-react/issues/255](https://github.com/asyncapi/asyncapi-react/issues/255), issue is postponed until [React component](https://github.com/asyncapi/asyncapi-react) is refactored to use the majority of types from the [parser-js](https://github.com/asyncapi/parser-js).**

To achieve only lazy loading of images, native browser functionality can be used. MDN documentation reads: *The `loading` attribute on an `` element ... can be used to instruct the...

Loading improvement for mobile users is obvious.  

Bounty Issue's End Of Life (EOL): [2024-02-29 23:59:59 UTC-12:00](https://time.lol/#2024-02-29T23:59:59-12:00)

### Bounty Issue's Timeline |Complexity Level|Assignment date (by GitHub)|Start date (by BP rules)|End date (by BP rules)|Draft PR submission|Final PR submission|Final PR merge| |----------------|---------------------------|------------------------|----------------------|-------------------|-------------------|--------------| |Medium |2023-11-07 |2023-11-13 |**2023-12-22** |2023-11-24 |2023-12-08...

Or, since it is CLI, which is text-only by default, there might be a text-only (non-graphical) description of changes utilizing GitHub's terminal font (with three backticks) on ``` - Improving...

If I were doing this code-related strictly textual UI/UX design task as a non-coder, I would still use VSCode to take a look at the `errors` directory, `catch` and `error`...

@asyncapi/bounty_team

### Bounty Issue's Timeline Extended |Complexity Level|Assignment date (by GitHub)|Start date (by BP rules)|End date (by BP rules)|Draft PR submission|Final PR submission|Final PR merge| |----------------|---------------------------|------------------------|----------------------|-------------------|-------------------|--------------| |Medium |2023-11-07 |[2023-11-13](https://time.lol/#2023-11-13T00:00:00+12:00) |**[2024-01-05](https://time.lol/#2024-01-05T23:59:59-12:00)** |[2023-11-24](https://time.lol/#2023-11-24T23:59:59-12:00)...