ilyakooo0/ormolu
1
0
Fork 0
mirror of https://github.com/ilyakooo0/ormolu.git synced 2024-09-19 20:57:17 +03:00
Code Issues Projects Releases Wiki Activity
145f7296f5
ormolu/CHANGELOG.md

119 lines
4.7 KiB
Markdown
Raw Normal View History

Preserve grouping of do statements
2020-04-16 14:40:13 +03:00
## Unreleased
* Grouping of statements in `do`-blocks is now respected. [Issue
74](https://github.com/tweag/ormolu/issues/74).
Version bump (0.0.4.0) [skip ci]
2020-04-15 16:52:50 +03:00
## Ormolu 0.0.4.0
Don't give up on first failure when multiple files are given Closes #502.
2020-01-27 23:47:14 +03:00
* When given several files to format, Ormolu does not stop on the first
failure, but tries to format all the files. [Issue
502](https://github.com/tweag/ormolu/issues/502).
Make rendering of operator patterns consistent with other cases
2020-01-31 16:18:57 +03:00
* Made rendering of pattern matches involving operators consistent with
other cases of rendering of operators. [Issue
500](https://github.com/tweag/ormolu/issues/500).
More compact rendering of type family injectivity constraints
2020-02-01 21:42:13 +03:00
* More compact rendering of type family injectivity constraints. [Issue
482](https://github.com/tweag/ormolu/issues/482).
Improve rendering of "where" in class declarations and such
2020-02-10 12:50:59 +03:00
* Improved rendering of the keyword `where` in class, data, and type family
declarations. When headers of these declarations are multi-line `where` is
now put on its own line. [Issue
509](https://github.com/tweag/ormolu/issues/509).
Fix rendering of arrow notation with multiline expressions
2020-04-10 13:33:22 +03:00
* Fixed the bug pertaining to rendering of arrow notation with multiline
expressions. [Issue 513](https://github.com/tweag/ormolu/issues/513).
Render type applications similar to value applications
2020-04-10 15:12:53 +03:00
* Made rendering of data type definitions, value-level applications, and
Do not lump together forall and constructors when deciding on layout
2020-04-10 15:29:27 +03:00
application of types use the same style. Moreover, existential now doesn't
Some minor edits to the changelog [skip ci]
2020-04-14 23:41:47 +03:00
cause the data constructor be unconditionally rendered in multiline
layout. [Issue 427](https://github.com/tweag/ormolu/issues/427).
Render type applications similar to value applications
2020-04-10 15:12:53 +03:00
Format records with a single data constructor more compactly
2020-04-10 18:52:25 +03:00
* Records with a single data constructor are now formatted more compactly.
[Issue 425](https://github.com/tweag/ormolu/issues/425).
Add the recent changes to the changelog [skip ci]
2020-04-09 19:37:02 +03:00
* Switched to `ghc-lib-parser-8.10.1`.
Some minor edits to the changelog [skip ci]
2020-04-14 23:41:47 +03:00
* Implemented support for the new language extensions `ImportQualifiedPost`
and `StandaloneKindSignatures`.
Version bump (0.0.3.1) [skip ci]
2020-01-22 21:17:34 +03:00
## Ormolu 0.0.3.1
Add a mention of the issue 498 to the changelog [skip ci]
2020-01-17 14:06:43 +03:00
* Fixed rendering of record updates with the record dot preprocessor syntax
[Issue 498](https://github.com/tweag/ormolu/issues/498).
Version bump (0.0.3.0) [skip ci]
2020-01-11 15:06:12 +03:00
## Ormolu 0.0.3.0
Mention the fix for #473 in the changelog [skip ci]
2019-12-03 13:12:10 +03:00
* Fixed an issue related to unnecessary use of curly braces. [Issue
473](https://github.com/tweag/ormolu/issues/473).
Fix application of multi-way if to arguments
2020-01-06 17:54:47 +03:00
* Fixed the issue with formatting multi-way if when it happens to be a
function applied to arguments [Issue
488](https://github.com/tweag/ormolu/issues/488). This changed the way
multi-line if is formatted in general.
Mention support for record dot syntax in the changelog [skip ci]
2020-01-07 18:38:57 +03:00
* Added support for record dot pre-processor when used via the plugin.
[Issue 486](https://github.com/tweag/ormolu/issues/486).
Do not hang record constructors Previously we hanged record constructors but not record updates. It looks like unlike other hanging constructions (lambdas, case expressions, and do-blocks), record constructors and updates should rather be placed normally. Indeed, when we stop hanging them, many constructions start to look more reasonable and predictable (see the updated test cases). Yet the change is not enough to fix the problem in general case: it is enough to replace the record with a e.g. do-block to get the same failure. To correct that we adjust what should fit in one line for hanging placement to fire: now we consider the span between beginning of function and the start of potentially-hanging construction.
2020-01-09 21:26:02 +03:00
* Stopped hanging record constructors and improved placing
potentially-hanging consturctions in the presence of comments. [Issue
447](https://github.com/tweag/ormolu/issues/447).
Fix indentation in presence of type applications
2020-01-10 18:27:03 +03:00
* Fixed indentation in presence of type applications. [Issue
493](https://github.com/tweag/ormolu/issues/493).
Preserve newlines in class and instance declarations Preserve user-added newlines with the following normalizations: * No newlines below where * Consecutive newlines are compressed into a single newline * Always surround documented declarations with blank lines
2019-12-06 23:41:52 +03:00
* Class and instance declarations now do not have a blank line after
`where`. Grouping of methods from the original input is also preserved
with some normalizations. [Issue
431](https://github.com/tweag/ormolu/issues/431).
Version bump (0.0.2.0) [skip ci]
2019-11-29 19:40:05 +03:00
## Ormolu 0.0.2.0
Add the fix for #408 the changelog [skip ci]
2019-10-26 15:20:59 +03:00
Migrate to ‘ghc-lib-parser’ This would let us have features from GHC 8.8.1 while still using GHC 8.6.5 from Nixpkgs. Bonus: Ormolu will be compilable with GHCJS.
2019-10-27 15:58:13 +03:00
* Switched to `ghc-lib-parser` instead of depending on the `ghc` package
directly. This should allow us to use newest features of GHC while not
necessarily depending on the newest version of the compiler. In addition
to that Ormolu is now GHCJS-compatible.
Restore ‘--ghc-opt’ options again, report unrecognized options While migrating to ‘ghc-lib-parser’ we accidentally stopped taking into account the ‘--ghc-opt’ options. This commit fixes that and makes sure we do not ignore unrecognized GHC options.
2019-11-02 14:34:46 +03:00
* Now unrecognized GHC options passed with `--ghc-opt` cause Ormolu to fail
(exit code 7).
Add the fix for #420 to the changelog [skip ci]
2019-10-27 15:49:20 +03:00
* Fixed formatting of result type in closed type families. See [issue
420](https://github.com/tweag/ormolu/issues/420).
Add the fix for #408 the changelog [skip ci]
2019-10-26 15:20:59 +03:00
* Fixed a minor inconsistency between formatting of normal and foreign type
signatures. See [issue 408](https://github.com/tweag/ormolu/issues/408).
Fix moving comments before module header into the export list
2019-11-01 19:58:26 +03:00
* Fixed a bug when comment before module header with Haddock was moved
inside the export list. See [issue
430](https://github.com/tweag/ormolu/issues/430).
Preserve empty ‘forall’s
2019-11-02 16:57:56 +03:00
* Empty `forall`s are now correctly preserved. See [issue
429](https://github.com/tweag/ormolu/issues/429).
Mention the issue 446 in the changelog
2019-11-17 14:21:52 +03:00
* Fixed [issue 446](https://github.com/tweag/ormolu/issues/446), which
involved braces and operators.
Insert comments between declarations and their preceding Haddocks I originally thought it's a good idea to prevent this, but it looks like it makes things arguably worse in certain cases even though the Haddocks end up not associated with their declarations (but they are not associated with them in the input either, so it's OK).
2019-11-19 13:31:25 +03:00
* When there are comments between preceding Haddock (pipe-style) and its
corresponding declaration they are preserved like this in the output
instead of being shifted. To be clear, this is not a very good idea to
have comments in that position because the Haddock will end up not being
associated with the declarations. Issues
[440](https://github.com/tweag/ormolu/issues/440) and
[448](https://github.com/tweag/ormolu/issues/448).
Implement correct handling of shebangs Also: rename and document some functions we took from ‘ghc-exact-print’.
2019-11-21 19:35:52 +03:00
* Implemented correct handling of shebangs. [Issue
377](https://github.com/tweag/ormolu/issues/377).
Handle stack headers correctly More about the feature: https://docs.haskellstack.org/en/stable/GUIDE/#script-interpreter
2019-11-28 13:21:42 +03:00
* Implemented correct handling of stack headers. [Issue
393](https://github.com/tweag/ormolu/issues/393).
Take non-commutative nature of language pragmas into account The order in which language pragmas are put in the input sometimes matters. This is because some language extensions can enable other extensions, yet the extensions coming later in the list have the ability to change it. So here we classify all extensions by assigning one of the four groups to them. Then we only sort inside of the groups.
2019-11-28 18:30:14 +03:00
* Sorting language pragmas cannot not change meaning of the input program
anymore. [Issue 404](https://github.com/tweag/ormolu/issues/404).
Mention the fix for #444 in the changelog [skip ci]
2019-11-29 19:38:14 +03:00
* Fixed formatting of applications where function is a complex expression.
[Issue 444](https://github.com/tweag/ormolu/issues/444).
Initial commit
2018-11-25 16:34:28 +03:00
## Ormolu 0.0.1.0
* Initial release.
Reference in New Issue Copy Permalink