solid

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

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

Why don't you use Hilt? Google says

Dagger and Hilt code can coexist in the same codebase. However, in most cases it is best to use Hilt to manage all of your usage of Dagger on Android.

Environment

• Server version: css2, css3

Description

An unlikely edge case, but I was able to create pod named idp , but then could not access it as it is the registration endpoint.

Should it be fixed with a pod name blacklist? If such a blacklist exists it could also include anti-phishing pod names such as ipd, account-recovery etc..

Hi!
It's possible to add, to automatic generate a version of WebApi with auth ( JWT for example ) and policys ?

If you know any answer for questions in README.MD, feel free to create a PR for adding a link to the answer!
Also, if you want to create your own answer, you are free to create a folder Answers/Technical, and create a document there in the same way as it is done for this [non-tech question](https://github.com/d1mnewz/interviews/blob