Skip to content

Making rendering useful for formatting files (2) #454

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

Merged
merged 5 commits into from
Jun 25, 2025
Merged

Conversation

ekrich
Copy link
Owner

@ekrich ekrich commented Jun 11, 2025

I messed up adding to your PR @kastoestoramadus

See #438

Just looking into this and rendering is a very popular topic and never tackled. I think we need to review and be confident we are not getting into a can of worms unless you plan to help me on some of the render issues and requests.

I am still leaning towards accepting this PR but would like you thought on some of the issues raised and other issues and PRs already brought up.

PRs

@ekrich ekrich changed the title Making rendering useful for formatting files. Making rendering useful for formatting files (2) Jun 11, 2025
@ekrich
Copy link
Owner Author

ekrich commented Jun 13, 2025

Ping @kastoestoramadus - what do you think?

@kastoestoramadus
Copy link
Contributor

Sure, not sure if I fix all of them but will solve some of them.
Thanks.

@ekrich
Copy link
Owner Author

ekrich commented Jun 24, 2025

I made some changes to your code - they look ok? I was just pointing out that we are going a new direction and there could be some bumps in the road. Maybe the lightbend library will accept your changes but who knows. Let me know how it goes with your tool after I make a release.

@@ -37,7 +36,7 @@ object ConfigRenderOptions {
case class FormattingOptions(
keepOriginOrder: Boolean = false,
doubleIndent: Boolean = true,
doubleColonAssign: Boolean = false,
colonAssign: Boolean = false,
Copy link
Contributor

Choose a reason for hiding this comment

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

👍

Copy link
Contributor

@kastoestoramadus kastoestoramadus Jun 25, 2025

Choose a reason for hiding this comment

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

plus you've covered defaults with tests. Your changes look good

@kastoestoramadus
Copy link
Contributor

kastoestoramadus commented Jun 25, 2025

Polish Scala community said not to count on Lightbend with their library.
Accpeted are only some version bumps of dependant libs and from known people only.

@kastoestoramadus
Copy link
Contributor

kastoestoramadus commented Jun 25, 2025

With my current employer I got some spare time at work. I'll look from time to time to this repo to help a bit.
I've added some comments to poeple in old repo. Maybe they'll contribute as well :).
Lets give them some time to react with their issues.

@ekrich
Copy link
Owner Author

ekrich commented Jun 25, 2025

Thanks for the review. They finally recently took new changes.

@ekrich ekrich merged commit 33f4607 into main Jun 25, 2025
3 checks passed
@ekrich ekrich deleted the formatting-prepare branch June 25, 2025 20:57
@ekrich
Copy link
Owner Author

ekrich commented Jun 25, 2025

Can be tested using 1.11.0-SNAPSHOT.

@ekrich
Copy link
Owner Author

ekrich commented Jun 25, 2025

@kastoestoramadus Sorry to bug you but I think I would have to add this feature before I can release to maintain source compatibility with lightbend/config with this PR as seen here - lightbend/config#798

They added a boolean before your latest rendering edition. I do have a Discord for sconfig - see link on main README.md or here if you do Discord. https://discord.gg/pKUzfFNq - Otherwise, I created an issue if you have any suggestions or comments - I can do the change. Issue: #455

@kastoestoramadus
Copy link
Contributor

kastoestoramadus commented Jul 9, 2025

@ekrich ok, will do it. Starting the work on it.

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