Skip to main content

factory functions vs decorator

const comicBookCharacter = ( first, last ) => {
const firstName = first
const lastName = last
return {
realName: `${firstName} ${lastName}`
}
}
const superPower = ( ref ) => {
let powers = []
return {
addPower: ( p ) => {
powers.push( p )
return ref
},
powers
}
}
const utilityBelt = ( ref ) => {
let utilities = []

return {
addToBelt: ( p ) => {
utilities.push( p )
return ref
},
utilities
}
}
const decorate = ( obj, factoryArray ) => {
const instances = factoryArray.map( f => f( obj ) )
return Object.assign( obj, …instances )
}
let batman = comicBookCharacter( ‘Bruce’, ‘Wayne’ )console.log( batman.realName )decorate( batman, [ superPower, utilityBelt ] )batman
.addPower( ‘money’ )
.addToBelt( ‘something’ )
.addPower( ‘strength’)
.addToBelt( ‘batarang’ )
console.log( batman.powers, batman.utilities )

Comments

Popular posts from this blog

About GraphQL - Downside

Web caching complexity

File uploading. Since GraphQL doesn’t understand files, a file uploading feature is not included in its specification. You won’t have to deal with this limitation in case of REST, as there you can POST or PUT whatever content you want to.
To allow file uploads in your GraphQL web app, there are several options: using Base64 encoding. But it will make the request larger and expensive to encode/decode.making a separate API endpoint just for this purpose.using a library like Apollo for implementing the GraphQL multipart request specification.uploadFileToS3:combineResolvers( // isAuthenticated, async (parent, args, { models }) => { const { file } = awaitargs const { createReadStream, filename, mimetype, encoding } = awaitfile conststream = createReadStream() constresult = awaituploadFileToS3(filename, stream) returnresult } ),