Website or app

https://developer.chrome.com/blog/mv2-transition/

Repro steps

Use latest React DevTools with Electron (Chromium) (18.2.0 / Chromium 100)

  (node:80082) ExtensionLoadWarning: Warnings loading extension at ./node_modules/electron-devtools-vendor/extensions/react-developer-tools:
    Manifest version 2 is deprecated, and support will be removed in 2023. See https://

The Storybook API has changed quite a lot since Solid's Storybook docs were written in 2019. It would be really helpful (and I think go a loooong way toward helping drive adoption, long-term) if Solid could:

1. Update the docs to reflect the latest Storybo

Most items coming from questions on the community forum

• a proper multicategory bar example based on https://community.plotly.com/t/multicategory-axis-type-example/26392
• example of shape or annotation covering several subplots thanks to xref='paper'. Also the shapes and annotations tutorial should link to each other.
• orthographic projection example in 3d axes tutorial (or

Saw this rule in the clj-kondo linter, and I think it would be a good addition to our strict mode. Having duplicate elements in sets is probably always a mistake in a production policy, and while it's "harmless", the intent is likely to provide another element rather than the duplicate, leading to an unexpected

bindings: {
  [index: string]: {
    arguments: string[],
    code: string
  };
}

in order to allow devs to change the event name we need to get the arguments from jsx and rewrite the code in the generator.

This PR is an example of that without arguments
BuilderIO/mitosis#323

Describe the issue

Currently its hard to debug errors in sandbox and demo environments if the installation fails during helm installation .
Enable verbose logging for helm commands and also kubectl commands

https://kubernetes.io/docs/reference/kubectl/cheatsheet/#kubectl-output-verbosity-and-debugging

The default option should be with this flag off.

 flytectl demo start

Right now the tutorial is coherently designed, tested, and even documented. However, it doesn't build up in a way that's very beginner friendly. It establishes glom's value and then immediately uses it at an intermediate level.

I'd like it if it was a bit more drawn out to use basic features first and then add a multi-line Coalesce as the

This is a part of #11

I decided to extract it since it is a big feature.

As a SDET
I want a documentation or Wiki page where the expected vs actual field matching is explained
So that I can use these in my test automation to test the server response payloads and headers
e.g. id=123 , id="123", isValid=true, isValid="true" etc

AC1:

Cover the following currently supported mechanisms with examples

• $EQ
• (int)
• (float) or (decimal)
• (boolean)

Hey guys, thanks for the great bindings... I was really starting to miss formik ;-)

So I've noticed there was a bit of refs discussion about a year ago:
jannikbuschke/formik-antd#123

and it seems like the inputs got some special ref love, but the select didnt - any chance of adding ref support to all components?

The Generated Client API is remains largely undocumented...

It would also be awesome if we could include the documentation of the API in the Generated DSL

seems like this is triggering drop / add

- create unique index tbl_x_y on levels(x, y);
+ create unique index tbl_x_y on levels (x, y);

and it shouldn't