Eric Burel

The use case is a big nested object living in the state: ```js { project: { widgets: [...], pages: [...], metaData: {...}, layouts: [...]} // and the list goes on...

Yeah definitely, I think a link to this ticket in the Readme would probably be sufficient, given that only legacy apps are concerned. I've updated the code with a small...

I seem to have a similar issue when setting up Material UI SSR + next-i18nnext SSR. The way Apollo detects SSR seems to be broken in certain scenarios when playing...

Solution from @as-zlynn-philipps sounds great, but this is a fix at Storybook level. Eventhough TS seems to accept ".js" even when the source a ".ts", you probably want to improve...

You seem to have 3 pages that are not completely consistent: - https://deno.land/[email protected]/getting_started/installation: from the getting started page, lists the "scripts" approaches + OS specific approaches but not asdf. -...

Ah didn't know that limitation indeed. So at least it would be worth making the documentation consistent, and perhaps recommend Asdf only for unix systems + Windows for WSL for...

Hey folks, I just want to point out that I've spent some time during the last years to formalize a pattern similar to what @timneutkens describes, I name it [Segmented...

It's related to Apollo2 SSR changes. I am merging and updating the package into the core right now. See PR #51 Sorry for the headache @enzolutions ^^

This behaviour is due to lines 34 to 36 of the file api/response/serverError.js `if (sails.config.environment === 'production' && sails.config.keepResponseErrors !== true) { data = undefined; }` Meaning that data passed...

This does not seem to work with correctly with some .svg files