Summary

This is task list issue.
"Blocks" fixture app which made by built-in API, 'react-fetch', Server Component combination that useful to play new features v18 later.

But current one is broken because importing removed older Cache API mo

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

Expected Behavior

At https://github.com/open-policy-agent/opa/blob/main/bundle/bundle_test.go#L31, the result of function Equal not used:

m.rootSet().Equal(stringSet{"x/y": struct{}{}, "y/z": struct{}{}})

while this function has no side effect:

func (ss stringSet) Equal(other stringSet) bool 

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

Describe the issue

For every master merge, we create a new release. We also generate docs and create PR for every master merge.

We want to avoid release workflow in case of docs or boilerplate PR.

What if we do not do this?

We have extra releases that only have docs changes, which isn't desirable.

Related component(s)

Flytectl

Are you sure this issue hasn't b

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)

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