Skip to content

Commit

Permalink
pass verbose
Browse files Browse the repository at this point in the history
  • Loading branch information
domluna committed Oct 7, 2024
1 parent f86aa44 commit 965ab02
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 3 deletions.
2 changes: 1 addition & 1 deletion Project.toml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name = "JuliaFormatter"
uuid = "98e50ef6-434e-11e9-1051-2b60c6c9e899"
authors = ["Dominique Luna <[email protected]>"]
version = "1.0.61"
version = "1.0.62"

[deps]
CSTParser = "00ebfdb7-1f24-5e51-bd34-a7502290713f"
Expand Down
5 changes: 3 additions & 2 deletions src/JuliaFormatter.jl
Original file line number Diff line number Diff line change
Expand Up @@ -436,8 +436,9 @@ function format(paths, options::Configuration)::Bool
end

function format(path::AbstractString; verbose::Bool = false, options...)
formatted =
format(path, Configuration(Dict{String,Any}(String(k) => v for (k, v) in options)))
config = Dict{String,Any}(String(k) => v for (k, v) in options)
config["verbose"] = verbose
formatted = format(path, Configuration(config))
if verbose && formatted
println("Well done! ✨ 🍰 ✨")
end
Expand Down

4 comments on commit 965ab02

@domluna
Copy link
Owner Author

@domluna domluna commented on 965ab02 Oct 7, 2024

Choose a reason for hiding this comment

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

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request created: JuliaRegistries/General/116725

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v1.0.62 -m "<description of version>" 965ab02bfe67ca22574c13489268d635046285e6
git push origin v1.0.62

Also, note the warning: Version 1.0.62 skips over 1.0.61
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@domluna
Copy link
Owner Author

Choose a reason for hiding this comment

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

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

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

Registration pull request created: JuliaRegistries/General/117021

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v1.0.62 -m "<description of version>" 965ab02bfe67ca22574c13489268d635046285e6
git push origin v1.0.62

Please sign in to comment.