Exploring Effect: Converting Github Actions to Effect for Vercel's Edge Config API
Hey, I really enjoyed Effect Days and I'm eager to give Effect a spin. I'm trying to get started by converting one of our Github Actions to Effect!
I'd be extremely curious to see what this would ideally look like. I tried a few approaches myself but didn't end up with anything worth showing.
This function
- reads inputs using core.getInput
- then reads a local file
- then makes a request to Vercel's Edge Config API providing the file contents as a request body
- and finally sets either the output (setOutput) or the failure reason (setFailed)
Where I'm stuck
- would this typically be one large pipe or multiple smaller ones?
- how do i keep multiple variables around so I can reference them later?
Could anybody rewrite this with Effect? Having this as an example of how to deal with a multi-step workflow would answer so many questions.
The original implementation is here https://gist.github.com/dferber90/ffa1e7d86d908a38e7b97bc52cb84a11
I'd be extremely curious to see what this would ideally look like. I tried a few approaches myself but didn't end up with anything worth showing.
This function
- reads inputs using core.getInput
- then reads a local file
- then makes a request to Vercel's Edge Config API providing the file contents as a request body
- and finally sets either the output (setOutput) or the failure reason (setFailed)
Where I'm stuck
- would this typically be one large pipe or multiple smaller ones?
- how do i keep multiple variables around so I can reference them later?
Could anybody rewrite this with Effect? Having this as an example of how to deal with a multi-step workflow would answer so many questions.
The original implementation is here https://gist.github.com/dferber90/ffa1e7d86d908a38e7b97bc52cb84a11
Similar Threads
Was this page helpful?
