Build complex rules, serialize them as JSON, and execute them in Scala
This little project aims to solve the following problems:
- Make stuff more awesome.
- Remove the less awesome stuff from your project.
Add the Sonatype.org Releases repo as a resolver in your build.sbt
or Build.scala
as appropriate.
resolvers += "Sonatype.org Releases" at "https://oss.sonatype.org/content/repositories/releases/"
Add Json Logic Scala as a dependency in your build.sbt
or Build.scala
as appropriate.
libraryDependencies ++= Seq(
// Other dependencies ...
"com.github.celadari" %% "JsonLogicScala" % "0.0.1" % "compile"
)
This project is compiled, tested, and published for the following Scala versions:
- 2.9.1
- 2.9.1-1
- 2.9.2
- 2.9.3
- 2.10.3
- 2.11.12
- 2.12.6
To use Json Logic Scala, you should import it and call it...
The Scaladoc API for this project can be found here.
package org.example
import com.github.celadari.jsonlogicscala._
case object MyObject {
// ...
}
Below is a list of features we would like to one day include in this project
- Support more awesome.
- Decimate the not-awesome.
Json Logic Scala is licensed under the MIT License.
MIT License
Copyright (c) 2019 celadari
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.