Environment:

• macOS 11.0.1 Big Sur, on an Apple Silicon (M1) chip
• React 17.0.1
• React DevTools 4.10.1, running in standalone mode via Electron 11.1.0 (darwin-arm64 build)
• New project using create-react-app . with the useScript hook to add the <script> tag required by React DevTools.

Steps to reproduce

1. Add React DevTools to a project with npm install --save react-devtools

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

I'd like to use react-solid-state in a React/Typescript project, but the typing are missing. Or do I have to import the types from solid?

The --claims-file file argument for opa build/sign is explained like this:

--claims-file string        set path of JSON file containing optional claims (see: https://openpolicyagent.org/docs/latest/management/#bundle-signature-format

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

It may be nice to ultimately just update these tests to read the data/blocks dir and run tests against each automatically so it's easier to manage these tests

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)

It would be nice to optionally be possible to tell the FormikDebug component to render in production mode anyway.

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

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