Do you want to request a feature or report a bug?
Bug

What is the current behavior?
I'm seeing "Error: Should not already be working" after upgrading to React 16.11

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

This is exclusively happening on an older version of Chrome, 68.0.3440 on Windows 7

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

Currently, whenever there's a patch release, like 0.36.1, that becomes the only displayed docs version in the version picker:

That's fine. However, we also stop generating website content for the previous versions, so 0.36.0 disappears: https://www.openpolicyagent.org/docs/v0.36.

Here is an example:
https://github.com/BuilderIO/mitosis/pull/266/files#diff-d77df8a4086c893b4cd3954952a7598b6f85dcab3ef5f5a7116c30ba589b467eL13

If we import a function like this:

import { getMitosisConfig } from 'src/helpers/get-mitosis-config';

TS and our local env & CI won't complain.

However, our production build will actually break. We need the import to be a rel

Describe the issue

Currently we run the Linter CI for golang repos using the golang-ci-linter binary. But according to the documentation it is faster and better to use the github action.
https://golangci-lint.run/usage/install/

The UX of all the error highlighting is also better.

What if we do not do this?

Finding linter errors is troublesome as users have to parse through the cons

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