As a result: libraries that cross-compile to ScalaJS are in a mess and we have a new Typesafe Config wrapper library basically EVERY DAY.
-
-
Bottom line: intentions were good, result is a mess and in many cases the features of HOCON are not even necessary.
1 reply 0 retweets 1 like -
I have been putting config directly into Scala code for over a decade. No complaints!
2 replies 0 retweets 3 likes -
Replying to @propensive @mfukar
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.
1 reply 0 retweets 1 like -
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.
1 reply 0 retweets 0 likes -
WTF
1 reply 0 retweets 0 likes -
Long story, but in short: https://github.com/olafurpg/metaconfig … is currently broken on ScalaJS, so I had to improvise.
1 reply 0 retweets 0 likes -
The other part of the story is that in HOCON defaults should be in hocon not in code. Not doing that & wanting to cross-build to Scala.js...
1 reply 0 retweets 0 likes -
Yeah, we’re in a bad situation there. The principle of least power would suggest we just move to JSON in that case.
1 reply 0 retweets 0 likes -
I don't think JSON is a good language for configuration files.
4 replies 0 retweets 1 like
Doesn't that depend a lot on what you're configuring? Not sure JSON is universally inappropriate...
-
-
You can get away with using it a lot of time, sure. But AFAIK it wasn't built to be a config language.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.