PR #19108 caused some Suspense-related DevTools regressions (more info available on #19368) which we did not catch because of the fact that DevTools tests are only run against the version of React in master.

We should follow the precedent of the regression fixtures tests and have CI run DevTools tests against multiple

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

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

Expected Behavior

According to the documentation https://www.openpolicyagent.org/docs/v0.29.4/rest-api/#health-api GET /health?bundles HTTP/1.1 can be used to determine if bundle activation is ok or not.

Two codes are possible:

• 200 when it is ok
• 500 when it is not ok

Let's consider following configuration :

• a OPA server using bundle through the configuration file
• bundle

Describe the feature/command for flytectl
Currently flytectl supports the filtering of flyte objects and limits the default result set to 100.
Inorder to fetch next 100 results or any other limit set by the user, we need to support pagination

Provide a possible output or ux example

flytectl get launchplan -p flytectldemo -d development --page 1
flytectl get workflow -p flytectlde

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

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)

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

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