Skip to content

New action: actions/haskell-setup#20

Merged
regadas merged 3 commits intoregadas:masterfrom
JackKelly-Bellroy:actions/haskell-setup
Aug 28, 2020
Merged

New action: actions/haskell-setup#20
regadas merged 3 commits intoregadas:masterfrom
JackKelly-Bellroy:actions/haskell-setup

Conversation

@JackKelly-Bellroy
Copy link
Copy Markdown
Contributor

Adds a new action actions/haskell-setup, mapping to the github actions/setup-haskell. The name is swapped around for consistency with actions/java-setup in this repo, but it might be a bad idea to establish a pattern where the github-actions-dhall names differ from the actual names of actions. I'm willing to rename this to setup-haskell and also do java-setup -> setup-java if you think that's better.

I've also needed to import more things from prelude here. Let me know if you're happy with how I'm doing this, or if you'd rather some other way of getting the prelude (such as /deps/Prelude.dhall containing a single frozen import or something).

This PR is rebased atop #19, to hopefully avoid merge conflicts on the dhall SHA256s. Merge that first and the diff here won't have the cache noise. If you merge something else in-between, let me know and I will re-freeze and rebase this PR.

Copy link
Copy Markdown
Owner

@regadas regadas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@regadas
Copy link
Copy Markdown
Owner

regadas commented Aug 24, 2020

it might be a bad idea to establish a pattern where the github-actions-dhall names differ from the actual names of actions

I agree can you swap it around and rebase. If you could make a new PR for the java-setup that would be awesome.

@JackKelly-Bellroy
Copy link
Copy Markdown
Contributor Author

Rebased atop #21 which fixes the setup-foo vs foo-setup switcharound.

There are a couple of things I'd like to talk about before merge:

  1. The use of actions/HaskellSetup and actions/setup-haskell: do we want to push them into an actions record before they get too big? Having actions/ as a quasi-namespace feels a bit weird, and AFAIK we can't assemble record keys from Text or anything.
  2. setup-haskell would be the first step function to have a schema'd type as its argument. Are you OK with this, or should it accept a record-of-optionals? I feel like there's a lot of value to providing the default, so long as you're happy with the convention it establishes.

@regadas regadas merged commit d7d25ed into regadas:master Aug 28, 2020
@JackKelly-Bellroy JackKelly-Bellroy deleted the actions/haskell-setup branch August 28, 2020 10:18
@JackKelly-Bellroy JackKelly-Bellroy restored the actions/haskell-setup branch August 28, 2020 10:19
@JackKelly-Bellroy JackKelly-Bellroy deleted the actions/haskell-setup branch August 28, 2020 10:19
@JackKelly-Bellroy
Copy link
Copy Markdown
Contributor Author

Thanks. Also, I assume that since you've merged this PR, we're happy to have argument schemata, if I need to use those again on larger actions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants