One of our project's GatsbyJS server side rendering seems to have some issues with fin

The error seems to be on this line: <d

I guess we can define setContextState and <code class

Context and Server Side Rendering about constate HOT 5 CLOSED

codyaverett commented on May 28, 2024

Context and Server Side Rendering

from constate.

Comments (5)

diegohaz commented on May 28, 2024 2

The error seems to be on this line:

constate/src/Container.tsx

Line 168 in a548d72

state={state[context]}

That state comes directly from Provider and it's set there in the constructor:

constate/src/Provider.tsx

Line 63 in a548d72

state: initialState as State,

Have you wrapped your app with Provider?

Maybe the solution is to add state: {} here:

constate/src/Context.ts

Line 17 in a548d72

const Context = React.createContext({} as ContextState);

from constate.

diegohaz commented on May 28, 2024 1

I guess we can define setContextState and mountContainer as optionals.

from constate.

codyaverett commented on May 28, 2024

Modifying this line as you recommended solved our issues.

constate/src/Context.ts

Line 17 in a548d72

const Context = React.createContext({} as ContextState);

My solution was just this

const Context = React.createContext<Partial<ContextState>>({ state: {} });

What do you think @diegohaz ?

from constate.

diegohaz commented on May 28, 2024

I think that's OK. Do we really need Partial there?

from constate.

codyaverett commented on May 28, 2024

As I see it, it's either we have it like that as a partial, or we'd also need to define setContextState, and mountContainer in that createContext Call.

const Context = React.createContext<ContextState>({ state: {}, mountContainer: (...mountContainerParams) => void, mountContainer: { ...mountContainerProps } });

from constate.

Recommend Projects