Releases: sjbarag/brs
Releases · sjbarag/brs
v0.37.0
v0.36.0
v0.35.0
v0.34.0
v0.33.1
v0.33.0
v0.32.0
v0.31.0
v0.30.0
Features
- Support for
ifSGNodeField#getFields()
(#529). Thanks @sjbarag! - Support for
ifString#setString()
(#532). Thanks @alimnios72! - Support for
dim
statements (#531). Thanks @strattonbrazil! - Support for code coverage collection (#525)
Bug Fixes
- Previously, the
RoString
constructor wouldn't behave correctly if you didn't pass it an initial argument. Now, it does (#533)! Thanks @alimnios72! - The parser wasn't keeping track of the
else
token locations forif
statements. Now, it does (#527)!
BRS v0.29.0
Features
brs
now knows how to create anroDeviceInfo
object (#480)! Most of the data is mocked out, but it does respect the running system'sLOCALE
andTZ
environment variables. Thanks @phillmein23!brs
also learned about theScene
node, allowing for subclasses ofScene
to be created as-needed. Great work @phillmein23!brs
finally gained support forunobserveField
, as well asobserveFieldScoped
andunobserveFieldScoped
. It also preventsobserveField
/observeFieldScoped
from being called outside the context of a SceneGraphNode
, just like the reference implementation does. (#505 / #521 / #526 / #527)
Bug Fixes
brs
would previously report that componentScene
extends componentFoo
, when really it wasFoo
that extendedScene
(#519 / #520). Great catch @strattonbrazil!brs
now matches the Reference BrightScript Implementation (RBI) closer by returninginvalid
for calls tofindNode("")
(#523 / #524). Nice job @strattonbrazil!- Explicit
return
statements wihin anobserveField
callback no longer throw "return statement encountered" errors. (#508 / #522)
💚 Thanks! 💚
I work at @hulu and they let me and some colleagues hack on (and maintain) this project during work hours. Thanks for letting us do that!
🚚 We're Moving 🚚
Just a reminder that the main brs
repo is moving into the @hulu organization soonish! This should have no practical impact on the project's direction, its maintenance, or even the people involved. Over the past year all the day-to-day maintenance has been shared between me (@sjbarag) and a few colleagues during work hours; this migration is an acknowledgement of that maintenance team and all the hard work that's they've put in.
More details will be communicated as they become available, but if you have any questions feel free to file an issue or email me (use git log
to find my address 😛).