6 replies

Using Context for Authorization in Effect v4: Considerations and Pitfalls

I've been using the Context to provide authorisation,to the program with effect v3 like that:

export interface UserContext {
  readonly userId: number;
}

export const UserContext = Context.GenericTag<UserContext>("UserContext");

program.pipe(
  Effect.provideService(UserContext, userContextData.value)
)

export interface UserContext {
  readonly userId: number;
}

export const UserContext = Context.GenericTag<UserContext>("UserContext");

program.pipe(
  Effect.provideService(UserContext, userContextData.value)
)

It works well, and I can then use the UserContext in my effects and all the code would automatically be authorised.

But with the new effect v4 seems like conceptually it might be wrong to do that? Probably i could use the { local: true }, but was wondering if there are any hidden pitfalls of doing that?

Effect Community•2mo ago•

6 replies

ferossgp

Using Context for Authorization in Effect v4: Considerations and Pitfalls

I've been using the Context to provide authorisation,to the program with effect v3 like that:

export interface UserContext {
  readonly userId: number;
}

export const UserContext = Context.GenericTag<UserContext>("UserContext");

program.pipe(
  Effect.provideService(UserContext, userContextData.value)
)

export interface UserContext {
  readonly userId: number;
}

export const UserContext = Context.GenericTag<UserContext>("UserContext");

program.pipe(
  Effect.provideService(UserContext, userContextData.value)
)

Using Context for Authorization in Effect v4: Considerations and Pitfalls

Similar Threads

Using Context for Authorization in Effect v4: Considerations and Pitfalls

Similar Threads

Similar Threads

Similar Threads