mauricioklein/go-chainable

Chain function calls in Golang, with support to argument's feedback and error-handling

Hi 👋, I'm Mauricio

Fullstack Engineer, 🐣 in 🇧🇷, 🏠 in 🇪🇸

3x AWS Certified | Staff Software Enginner @ CommerceHub | ex-AWS

• 📝 I regularly write articles on mklein.io

• 💬 Ask me about React, NodeJS, Typescript, AWS, Serverless

• 📄 Know about my experiences on Linkedin

Connect with me:

Languages and Tools:

 

go-chainable's Issues

Panic when the last function in the chain has no return value

When the last function in the chain returns nothing, the system panics:

f1 := func() int { return 0 }
f2 := func(x int) {}

New().Chain(f1, f2).Unwrap()

For the case above, the Unwrap method is supposed to return any zero-value (like an empty string) and a nil error

Gracefully handle argument type mismatch

When the values provided by the chain to a function don't match the arguments type expected by the function, a panic is raised:

f1 := func() int { return 0 }
f2 := func(str string) {}

_, err := New().Chain(f1, f2).Unwrap()

The library should be able to identify such cases and raise a proper error in the chain.

Providing a "nil" value on "chain.From()" causes a panic

Providing a nil argument in chain.From() causes a panic:

// Using `Chain()`
New().From(nil).Chain(
   func (e error) error { return e },
).Unwrap()

// Using `ChainDummy()`
New().From(nil).ChainDummy(
   func (e error) error { return e },
).Unwrap()

The system should accept such values just fine and perform all the validations and logic as any other values provided to the chain.

Library doesn't support non-primitive types

For non-primitive types, the library panics:

type thing struct{}

f1 := func(t thing) thing { return t }
f2 := func(t thing) {}

New().From(thing{}).ChainDummy(f1, f2).Unwrap()

It is supposed to handle non-primitive values just fine, performing all the checkings as a primitive value today.