You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Update Scala versions
* Update to RC1, javatime, and scalafix
* Save snapshot and RC setting versions
* Add SN 0.5.0 and SJS 1.6.0
* Update scala-collection compat to 2.12, drop link stubs, and add URLConnection for stubs
* Update to Scala Native 0.5.1
* Update README for 1.7.0 release
Configuration library written in [Scala](https://www.scala-lang.org/) which is a direct translation
6
-
of the original widely used Java library.
5
+
Configuration library written in [Scala](https://www.scala-lang.org/) which is a direct translation of the original widely used Java library.
7
6
8
7
[Scala JVM](https://www.scala-lang.org/), [Scala Native](https://scala-native.readthedocs.io/), and [Scala.js](https://www.scala-js.org/)
9
8
are supported. Scala JVM is fully supported whereas the other platforms support a subset of the full API.
10
9
11
-
For motivation and background about this project see the [PR](https://github.com/lightbend/config/pull/600)
12
-
to the original project. The TLDR is the library was ported to Scala to support Scala Native so
13
-
[scalafmt](https://scalameta.org/scalafmt/) which uses HOCON configuration could be compiled into
14
-
a native application.
10
+
For motivation and background about this project see the [PR](https://github.com/lightbend/config/pull/600) to the original project. The TLDR is the library was ported to Scala to support Scala Native so [scalafmt](https://scalameta.org/scalafmt/) which uses HOCON configuration could be compiled into a native application.
15
11
16
-
Care has been taken to keep the API the same but changes were needed when moving from the Java API.
17
-
Using Java is also possible as demonstrated by including the working Java examples.
12
+
Care has been taken to keep the API the same but changes were needed when moving from the Java API. Using Java is also possible as demonstrated by including the working Java examples.
Please refer to the original library documentation [here](https://github.com/lightbend/config).
56
-
This is to reduce the maintenance burden of this library.
51
+
Please refer to the original library documentation [here](https://github.com/lightbend/config). This is to reduce the maintenance burden of this library.
57
52
58
-
The intent is to keep the library in sync with the original but each PR needs to be be ported
59
-
to maintain feature parity. The documentation could contain features that are not yet implemented
60
-
in this library.
53
+
The intent is to keep the library in sync with the original but each PR needs to be be ported to maintain feature parity. The documentation could contain features that are not yet implemented in this library.
61
54
62
55
For specific changes, refer to the releases below.
63
56
@@ -66,44 +59,34 @@ For specific changes, refer to the releases below.
66
59
[](https://index.scala-lang.org/ekrich/sconfig/sconfig)
This project publishes a [scalafix](https://scalacenter.github.io/scalafix/) rule to migrate
70
-
existing Scala 2 source code that uses `com.typesafe.config.Config` to this implementation.
71
-
Scalafix rules modify in place existing valid Scala code. Think of it as a fancy find-and-replace
72
-
tool that is aware of the Scala type system and can therefore narrowly tailor the changes
73
-
being made. (Since scalafix changes the source code on your file system, it's best to commit
74
-
any changes prior to running the rule, in case something weird happens.)
62
+
This project publishes a [scalafix](https://scalacenter.github.io/scalafix/) rule to migrate existing Scala 2 source code that uses `com.typesafe.config.Config` to this implementation. Scalafix rules modify in place existing valid Scala code. Think of it as a fancy find-and-replace tool that is aware of the Scala type system and can therefore narrowly tailor the changes being made. (Since scalafix changes the source code on your file system, it's best to commit any changes prior to running the rule, in case something weird happens.)
75
63
76
-
The rule will replace `com.typesafe.config` package references with `org.ekrich.config`,
77
-
and remove trailing parens on some methods (where the API changed from the Java implementation).
64
+
The rule will replace `com.typesafe.config` package references with `org.ekrich.config`, and remove trailing parens on some methods (where the API changed from the Java implementation).
78
65
79
-
Complete setup documentation and the current `scalafix` version can be found in the
80
-
[scalafix user guide](https://scalacenter.github.io/scalafix/docs/users/installation.html).
81
-
At a high level, the process is as follows:
66
+
Complete setup documentation and the current `scalafix` version can be found in the [scalafix user guide](https://scalacenter.github.io/scalafix/docs/users/installation.html). At a high level, the process is as follows:
82
67
83
68
1. Add scalafix to the project's `project/plugins.sbt` file using the version found above:
2. Add this project to the project's `libraryDependencies`, but don't remove the old one yet!
90
75
91
-
(The old dependency needs to stay on the classpath until after the rule runs, because the
92
-
code must compile before it will run.)
76
+
(The old dependency needs to stay on the classpath until after the rule runs, because the code must compile before it will run.)
93
77
94
-
3. Run the scalafix sbt command shown below to apply the rule using the version of `sconfig`
95
-
selected. Replace the `x.y.z` below with the version (must be greater than version `1.4.5`
96
-
when scalafix was added):
78
+
3. Run the scalafix sbt command shown below to apply the rule using the version of `sconfig` selected. Replace the `x.y.z` below with the version (must be greater than version `1.4.5` when scalafix was added):
0 commit comments