43 replies

Struggling with Refactoring Service Methods to Return Options

I decided to try to refactor some of my service methods to return

Option

Option

s found myself struggling a bit.

When I was just dealing with "normal"

Option

Option

s, it feels pretty straightforward:

pipe(
  // someFunc: (input: string) => Effect.Effect<never, never, Option.Option<SomeRecord[]>>
  getRecords(someInput),
  // ...grab the first record if it exists
  Effect.map(Option.flatMap(ReadonlyArray.head)),
  // ...parse the record
  Effect.map(Option.map(parseSomeRecord)),
)

pipe(
  // someFunc: (input: string) => Effect.Effect<never, never, Option.Option<SomeRecord[]>>
  getRecords(someInput),
  // ...grab the first record if it exists
  Effect.map(Option.flatMap(ReadonlyArray.head)),
  // ...parse the record
  Effect.map(Option.map(parseSomeRecord)),
)

But when I needed to start mixing in other effects without "breaking out" of

Option

Option

, it felt like a war between the "option" pattern (

Effect<never, never, Option<Something>>

Effect<never, never, Option<Something>>

) and the "effect" pattern (

Effect<never, SomethingNotFound, Something>

Effect<never, SomethingNotFound, Something>

).

I found something that seems to work, but was wondering if there are more idiomatic patterns that I'm perhaps missing?

(More details threaded)

Effect Community•3y ago•

43 replies

Thr1ve

Struggling with Refactoring Service Methods to Return Options

I decided to try to refactor some of my service methods to return

Option

Option

s found myself struggling a bit.

When I was just dealing with "normal"

Option

Option

s, it feels pretty straightforward:

pipe(
  // someFunc: (input: string) => Effect.Effect<never, never, Option.Option<SomeRecord[]>>
  getRecords(someInput),
  // ...grab the first record if it exists
  Effect.map(Option.flatMap(ReadonlyArray.head)),
  // ...parse the record
  Effect.map(Option.map(parseSomeRecord)),
)

pipe(
  // someFunc: (input: string) => Effect.Effect<never, never, Option.Option<SomeRecord[]>>
  getRecords(someInput),
  // ...grab the first record if it exists
  Effect.map(Option.flatMap(ReadonlyArray.head)),
  // ...parse the record
  Effect.map(Option.map(parseSomeRecord)),
)

But when I needed to start mixing in other effects without "breaking out" of

Option

Option

, it felt like a war between the "option" pattern (

Effect<never, never, Option<Something>>

Effect<never, never, Option<Something>>

) and the "effect" pattern (

Effect<never, SomethingNotFound, Something>

Effect<never, SomethingNotFound, Something>

).

I found something that seems to work, but was wondering if there are more idiomatic patterns that I'm perhaps missing?

(More details threaded)

Struggling with Refactoring Service Methods to Return Options

Similar Threads

Struggling with Refactoring Service Methods to Return Options

Similar Threads

Similar Threads

Similar Threads