Skip to content

Commit

Permalink
Preparing for 0.12.3 release
Browse files Browse the repository at this point in the history
  • Loading branch information
michbarsinai committed Jul 13, 2022
1 parent 0daeb8c commit 3bb8e8b
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,16 +55,16 @@ If you use BPjs in an academic work, please consider citing it as:
### 2022-07
* :arrow_up: :sparkles: Moved to Rhino 1.7.14. This means many new features, including template strings and better Java interoperability. See full list [on Mozilla's site](https://github.com/mozilla/rhino/releases/tag/Rhino1_7_14_Release). ([#186](https://github.com/bThink-BGU/BPjs/issues/186)).
* :part_alternation_mark: Refactored internals fo better fit the new Rhino version. We now have a proper context factory, as well as try-with-resources on all context invocations.
* :part_alternation_mark: `BProgramRunnerListener` defautls to ignores errors during BProgram execution, instead of printing the details to `stderr`. This behavior remains in `BProgramRunnerListenerAdapter`, where it makes more sense. At any event, client code can override these methods. ([#191](https://github.com/bThink-BGU/BPjs/issues/191)).
* :part_alternation_mark: `BProgramRunnerListener` defautls to ignore errors during BProgram execution, instead of printing the details to `stderr`. This behavior remains in `BProgramRunnerListenerAdapter`, where it makes more sense. Of course, client code can override these methods. ([#191](https://github.com/bThink-BGU/BPjs/issues/191)).
* :arrow_up: Printing problematic b-thread's name during serialization errors ([#169](https://github.com/bThink-BGU/BPjs/issues/169)).
* :sparkles: Custom serialization for the non-serializable `java.util.Optional` and JavaScript's `Set()`. ([#189](https://github.com/bThink-BGU/BPjs/issues/189))
* Also, this is a basis for custom serializations in general.
* :arrow_up: Improved warrping of Java objects as they come to JavaScript: Java strings are now treated as native JS strings, so using the `===` operator works as expected. ([#104](https://github.com/bThink-BGU/BPjs/issues/104)).
* :bug: Verification stops on ECMAScript errors ([#49](https://github.com/bThink-BGU/BPjs/issues/49)).
* :sparkles: Custom serialization for the common and non-serializable `java.util.Optional` and JavaScript's `Set()`. ([#189](https://github.com/bThink-BGU/BPjs/issues/189))
* This is a basis for custom serializations in general, we now have an initial mechanism in place.
* :arrow_up: Improved wrapping of Java objects as they come to JavaScript: Java strings are now treated as native JS strings, so using the `===` operator works as expected. ([#104](https://github.com/bThink-BGU/BPjs/issues/104)).
* :bug: Verification stops on ECMAScript errors, instead of hanging ([#49](https://github.com/bThink-BGU/BPjs/issues/49)).
* :bug: Improved error reporting when trying to sync outside of a b-thread ([#174](https://github.com/bThink-BGU/BPjs/issues/174)).
* :arrow_up: Informative error message when requesting a list of events and one of the events is `null` ([#184](https://github.com/bThink-BGU/BPjs/issues/184)).
* :arrow_up: Loggins is turned off by default during verification. Call `BPjs.setLogDuringVerification(true)` to enable them again ([#160](https://github.com/bThink-BGU/BPjs/issues/160)).
* :sparkles: Added local JACOCO code coverage reports.
* :arrow_up: Logging is turned off by default during verification. Call `BPjs.setLogDuringVerification(true)` to enable them again ([#160](https://github.com/bThink-BGU/BPjs/issues/160)).
* :sparkles: Added local [JACOCO](https://www.jacoco.org) code coverage reports.

### 2022-02 (Including the 1st BP Day Hackathon)
* :part_alternation_mark: Calling `bp.sync` from global scope during runtime does not cause an ugly exception anymore ([#174](https://github.com/bThink-BGU/BPjs/issues/174)). The error is reported to the listeners.
Expand Down

0 comments on commit 3bb8e8b

Please sign in to comment.