Impopular opinion: it’s borderline absurd that the Scala community uses its own config format.
-
Bottom line: intentions were good, result is a mess and in many cases the features of HOCON are not even necessary.
I have been putting config directly into Scala code for over a decade. No complaints!
-
-
Usually I need one input (e.g. an environment variable or checking hostname) to determine which of several code-based configs to use.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
In applications, I typically use HOCON just as a passthrough to ENV vars. But in CLI apps (e.g. scalafix, scalafmt) it’s a bit different.
-
For various reasons (HOCON being one of them), this happened: https://github.com/gabro/scalafmt/blob/5fc2308bb48cee681619510d4ee57d1e3ba0f482/scalafmt-jsfacade/src/main/scala/org/scalafmt/jsfacade/Config.scala#L16-L187 … It’s fixable, but it’s a bunch of hours thrown away.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.