Oso now supports applications written in Node.js, using our Node.js library. Download here.
This release contains breaking changes. Be sure to follow migration steps before upgrading.
x.foo() in an Oso policy could either be
performing an attribute lookup or invoking a zero-arity method on
looking up the
foo property returned a method, the host language libraries
would transparently invoke it and return the result.
As of this release, parentheses are required for invocation.
performs a lookup, and
x.foo() invokes a zero-arity method.
Oso can be run in debug mode by setting an environment variable
This prints debug output when polar queries are evaluated to show what’s
Other bugs & improvements
- Improved performance of policies with many rules having ground (constant) parameters.
- Improved performance of
inoperator (list membership) with many ground elements.
- Stack traces return the original policy source instead of the internal version.
- New FFI methods for passing print and warning messages from the core runtime to the language libraries.
Many thanks to Dan Callahan for the documentation suggestion!
Connect with us on Slack
If you have any questions, or just want to talk something through, jump into Slack. An Oso engineer or one of the thousands of developers in the growing community will be happy to help.