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

stylua 2.0.0 #198012

Merged
merged 2 commits into from
Nov 17, 2024
Merged

stylua 2.0.0 #198012

merged 2 commits into from
Nov 17, 2024

Conversation

clason
Copy link
Contributor

@clason clason commented Nov 17, 2024

Created with brew bump-formula-pr.

release notes
StyLua has officially stabilised to v2.0.0. With this, we make a commitment that the formatting output is fairly stable across minor version bumps. More details: https://github.com/JohnnyMorganz/StyLua/issues/459

Key Changes

This release updates the internal Lua parser, bringing performance improvements and new Luau syntax features.

LuaJIT is now separate from Lua5.2, with its own feature flag.

Runtime syntax selection

By default, StyLua runs with a parser that is able to handle a variety of different Lua syntaxes at once, with a goal of being easily usable on different codebases. However, there are times where 2 different syntax definitions conflict, introducing ambiguity. For example, Lua 5.2 label syntax (::label::) conflicts with Luau's type assertion syntax (x :: number), and the latter ends up taking priority.

Now, you can select a particular style of syntax at runtime to deal with these ambiguities.

In your stylua.toml file, add:

syntax = "Lua52" # Possible values: All, Lua51, Lua52, Lua53, Lua54, LuaJIT, Luau

Or, specify --syntax lua52 on the command line.

The default remains "All" to handle all syntaxes as much as possible.

More details: JohnnyMorganz/StyLua#407

Updated Configuration Resolution

Previously, StyLua would only search for a stylua.toml (or .stylua.toml) file in the directory where the binary was executed - the current working directory (or its ancestors, if --search-parent-directories is enabled). This means that any configuration files present in subdirectories are not taken into account.

This release changes config resolution to pick up stylua.toml files in subdirectories. Now, a file will format based on the stylua.toml configuration closest to its location. StyLua will search backwards from the file location to the current working directory for a configuration file. By default, searching will stop at the current working directory, however it will continue if --search-parent-directories is enabled.

More details: JohnnyMorganz/StyLua#916


[2.0.0] - 2024-11-17

Breaking Changes

  • For automated downloaders: the legacy release artifacts stylua-win64.zip, stylua-linux.zip and stylua-macos.zip are no longer produced in GitHub releases, in favour of more specific names (e.g., stylua-windows-x86_64, stylua-linux-x86_64 and stylua-macos-x86_64).
  • --stdin-filepath no longer respects ignore files by default, in line with passing files directly to the command line. Now, stylua --stdin-filepath foo.lua - will still format the stdin even if foo.lua was in a .styluaignore file. Use --respect-ignores to preserve the original behaviour.
  • Removed deprecated access patterns on Config struct in stylua Rust library

Added

  • Added runtime syntax configuration option syntax to help handle ambiguous syntax. By default, StyLua builds and runs with a parser to handle all Lua versions. However, the syntax of some Lua versions conflict with eachother: most notably, Lua 5.2+ goto label syntax ::label:: and Luau type assertion operator ::. This option allows choosing what syntax to parse, to handle these conflicts. (#407)
  • Added configuration option space_after_function_names to specify whether to include a space between a function name and parentheses (#839)

Changed

  • Update internal Lua parser version (full-moon) to v1.1.0. This includes parser performance improvements. (#854)
  • LuaJIT is now separated from Lua52, and is available in its own feature and syntax flag
  • .stylua.toml config resolution now supports looking up config files next to files being formatted, recursively going
    upwards until reaching the current working directory, then stopping (unless --search-parent-directories was specified).
    For example, for a file ./src/test.lua, executing stylua src/ will look for ./src/stylua.toml and then ./stylua.toml.
  • When collapse_simple_statement is enabled, if the enclosing block is a return, we will check if the return expression is "simple" (currently, not containing a function definition) (#898)

Fixed

  • Fixed formatting of method call chain when there is a comment between the colon token : and the function name (#890)
  • Removed accidental random print to stdout when formatting a return statement across multiple lines (#879)
  • Luau: Fixed incorrect removal of semicolon before compound assignment with parentheses leading to ambiguous syntax error (#885)
  • Luau: Fixed incorrect collapsing of union/intersection type value with comments in a type table leading to a syntax error (#893)
  • Fixed --verify panicing due to overflow for very large Hex numbers (#875, #889)

@github-actions github-actions bot added rust Rust use is a significant feature of the PR or issue bump-formula-pr PR was created using `brew bump-formula-pr` labels Nov 17, 2024
Copy link
Contributor

🤖 An automated task has requested bottles to be published to this PR.

@github-actions github-actions bot added the CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. label Nov 17, 2024
@BrewTestBot BrewTestBot added this pull request to the merge queue Nov 17, 2024
Merged via the queue into Homebrew:master with commit 7d35352 Nov 17, 2024
15 checks passed
@clason clason deleted the bump-stylua-2.0.0 branch November 17, 2024 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bump-formula-pr PR was created using `brew bump-formula-pr` CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. rust Rust use is a significant feature of the PR or issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants