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

Move 'other HOCON tools' to HOCON.md #515

Closed
wants to merge 1 commit into from

Conversation

raboof
Copy link
Contributor

@raboof raboof commented Oct 17, 2017

As they're relevant to everyone interested in HOCON, not specifically Typesafe
Config users

As they're relevant to everyone interested in HOCON, not specifically Typesafe
Config users
@raboof raboof force-pushed the moveToolsToHOCONmd branch from 12239d8 to 8ab794e Compare November 6, 2017 09:09
@raboof
Copy link
Contributor Author

raboof commented Nov 6, 2017

(rebased to fix conflict with #525)

@havocp
Copy link
Collaborator

havocp commented Nov 6, 2017

I’m a bit worried this lowers exposure and visibility for these tools, though I don’t have analytics to prove it, I’d imagine README gets more views. Maybe the README could be more explicit in saying that implementations for other languages can be found at this link?

@raboof
Copy link
Contributor Author

raboof commented Nov 13, 2017

Yes, I agree with that concern. My intent was in fact the opposite: I'm afraid someone not interested in Scala will see the README, assume it's "just some Scala library" and not get to this part at all. Similarly, someone who just googles for 'hocon' will find https://github.com/lightbend/config/blob/master/HOCON.md first and also miss these links.

I agree putting this in HOCON.md seems a bit 'buried'. I wonder if it'd make sense to create a separate (tiny) lightbend/hocon project describing the format and linking to various libraries, without any scala/typesafeconfig-specific parts?

Base automatically changed from master to main March 19, 2021 19:32
@raboof
Copy link
Contributor Author

raboof commented Aug 29, 2022

I agree putting this in HOCON.md seems a bit 'buried'. I wonder if it'd make sense to create a separate (tiny) lightbend/hocon project describing the format and linking to various libraries, without any scala/typesafeconfig-specific parts?

(I'd still be willing to do this, if y'all agree it would be helpful. closing this PR though :) )

@raboof raboof closed this Aug 29, 2022
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