Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nix dev shell: upgrade fourmolu-0.18.0 #1049

Merged
merged 3 commits into from
Feb 4, 2025

Conversation

carbolymer
Copy link
Contributor

Changelog

- description: |
    Nix dev shell: upgrade fourmolu-0.18.0
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - refactoring    # QoL changes
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
   - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context

Fourmolu 0.18 supports import grouping but there's no column-wise alignment yet, so we're still keeping stylish haskell around for formatting imports.

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated. See Running tests for more details
  • Self-reviewed the diff

@carbolymer carbolymer force-pushed the mgalazyn/chore/upgrade-fourmolu-0.18 branch 2 times, most recently from b7d9d11 to 314e5df Compare February 4, 2025 14:28
@carbolymer carbolymer force-pushed the mgalazyn/chore/upgrade-fourmolu-0.18 branch from 314e5df to db53aaa Compare February 4, 2025 14:28
@carbolymer carbolymer merged commit 2427f53 into master Feb 4, 2025
15 of 16 checks passed
@carbolymer carbolymer deleted the mgalazyn/chore/upgrade-fourmolu-0.18 branch February 4, 2025 14:28
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.

3 participants