From e526319a4e6df44a4f63ef53b5264a811f0dc10c Mon Sep 17 00:00:00 2001
From: rokucommunity-bot <93661887+rokucommunity-bot@users.noreply.github.com>
Date: Mon, 2 Dec 2024 01:07:01 +0000
Subject: [PATCH] What's new for 2024-11-November
---
src/pages/whats-new/2024-11-November.md | 321 ++++++++++++++++++++++++
1 file changed, 321 insertions(+)
create mode 100644 src/pages/whats-new/2024-11-November.md
diff --git a/src/pages/whats-new/2024-11-November.md b/src/pages/whats-new/2024-11-November.md
new file mode 100644
index 0000000..44ac0d6
--- /dev/null
+++ b/src/pages/whats-new/2024-11-November.md
@@ -0,0 +1,321 @@
+---
+date: November 2024
+summary: Changes to vscode-brightscript-language, brighterscript, promises
+layout: ../../layouts/WhatsNewPost.astro
+---
+# Overview
+Welcome to the November 2024 edition of "What's New in RokuCommunity." Please consider subscribing to stay up to date with what's happening in RokuCommunity.
+
+## We need your help
+The RokuCommunity projects are maintained by a relatively small group of developers (mostly volunteers), and we have a growing list of unresolved issues. We need your help! There are many different ways you can contribute. Whether it's addressing bugs, improving documentation, introducing new features, or simply helping us manage our expanding list of GitHub issues, your involvement would be greatly appreciated. We are more than happy to guide you in finding the most suitable contribution method that aligns with your interests. To learn more about how you can contribute, feel free to reach out to us on [Slack](https://join.slack.com/t/rokudevelopers/shared_invite/zt-4vw7rg6v-NH46oY7hTktpRIBM_zGvwA), or explore the existing GitHub issues:
+
+- [vscode-brightscript-language](https://github.com/rokucommunity/vscode-brightscript-language/issues)
+- [brighterscript](https://github.com/rokucommunity/brighterscript/issues)
+- [brighterscript-formatter](https://github.com/rokucommunity/brighterscript-formatter/issues)
+- [roku-deploy](https://github.com/rokucommunity/roku-deploy/issues)
+- [roku-debug](https://github.com/rokucommunity/roku-debug/issues)
+- [bslint](https://github.com/rokucommunity/bslint/issues)
+- [ropm](https://github.com/rokucommunity/ropm/issues)
+- [brs](https://github.com/rokucommunity/brs/issues)
+- [roku-report-analyzer](https://github.com/rokucommunity/roku-report-analyzer/issues)
+- [@rokucommunity/promises](https://github.com/rokucommunity/promises/issues)
+- [roku-http](https://github.com/rokucommunity/roku-http)
+
+## Issue of the month
+
+In this section, we highlight a specific issue where we could benefit from the community's assistance in finding a solution. These problems are generally straightforward to address, and serve as an excellent opportunity to become acquainted with the various RokuCommunity codebases.
+
+This month, we'd like to highlight [SOME_GH_ISSUE](SOME_URL). SOME_DESCRIPTION
+
+
+If you're interested in working on this feature, please comment on the [github issue](SOME_LINK) or reach out to us on [Slack](https://join.slack.com/t/rokudevelopers/shared_invite/zt-4vw7rg6v-NH46oY7hTktpRIBM_zGvwA)
+# Editor
+## Show multi-line lsp progress details
+
+
+Shows progress from the lsp busy status in the tooltip multi-line. This _should_ be backwards compatible with the existing status, but it also supports the `scope` property (mostly used to include project name).
+
+Looks like this:
+
+
+
+
+
+## Fix bug with m.top colorization
+
+
+Fixes syntax highlighting bug related to `.top`
+
+Before:
+
+
+After:
+
+
+
+
+
+# Debugging
+
+
+# BrighterScript
+
+## Optimize ternary transpilation for assignments
+
+
+Whenever a ternary expression is on the right-hand-side of an assignment, dottedSet, or indexedSet statement, we can transpile the entire thing to an `if` statement instead which improves performance significantly (should be identical to handwritten non-ternary code).
+
+This PR adds this `if` statement transpiling for all of the following situations:
+- assignments: `a = true ? 1 : 2`
+- dotted set: `m.a = true ? 1 : 2`
+- indexed set: `m["a"] = true ? 1 : 2`
+- complex assignment operators (i.e. `+=`, `-=`, etc...) `size += true ? 1 : 2`
+- grouped ternaries: `a = (((true ? 1 : 2)))`
+- nested ternaries `a = true ? (false ? 1 : 2) : 3`
+
+These are explicit cases, so any situation other than these will be transpiled according to the existing rules ([basic](https://github.com/rokucommunity/brighterscript/blob/master/docs/ternary-operator.md#basic-usage) and [scope safe](https://github.com/rokucommunity/brighterscript/blob/master/docs/ternary-operator.md#scope-protection))
+
+**Simple example:**
+```brighterscript
+a = true ? 1 : 2
+```
+
+becomes this:
+```brighterscript
+if true then
+ a = 1
+else
+ a = 2
+end if
+```
+
+**Nested example:**
+```brighterscript
+result = true ? (false ? "one" : "two") : "three"
+```
+
+becomes this:
+```brighterscript
+if true then
+ if false then
+ result = "one"
+ else
+ result = "two"
+ end if
+else
+ result = "three"
+end if
+```
+
+[This benchmark](https://github.com/rokucommunity/bsbench/blob/master/src/source/benchmarks/TernaryPerformance.bs) shows a significant improvement in performace
+
+
+
+
+
+
+## Fix issues with the ast walkArray function
+
+
+Fix a bug that doesn't properly recover when the array being walked changes.
+
+The core change in logic is as follows:
+ - during an AST walk, if the visitor returns a new node, we will not walk the original node's children, and instead walk the new node's children
+ - if a visitor changes an array (like `statements`), we will do a simple change detection method: `array[i] !== valuePassedToVisitor`. If we detect that it has changed, we'll restart the walk over that array (but skip any nodes we've already visited). This _can_ result in elements being visited out of order, but the use case for this is to help during transpile, so the order typically matters less.
+
+
+## Enhance lexer to support long numeric literals with type designators
+
+
+Fix lexer to support long numeric literals with type designators.
+
+Fixes #1350
+
+
+## [Proposal] Add Namespace Source Literals
+
+
+I'd like to add two source literals: `SOURCE_NAMESPACE` and `SOURCE_NAMESPACE_ROOT`
+
+- These are complimentary to the existing `SOURCE_FUNCTION_NAME` literal
+- These are very useful for trace logging
+- for developers that use a logger with filtering, enables filtering logs based on the namespace they originate from
+ - alternative right now is to use `PKG_PATH`, but that changes every file, whereas a namespace can span multiple files
+
+Live Transpile Preview (pulled from VSCode)
+
+
+### Brighterscript:
+```
+Sub ComponentScope ()
+ ' Component Scope
+ sourceFunction = source_function_name
+ sourceNamespace = source_namespace
+ sourceNamespaceRoot = source_namespace_root
+End Sub
+
+Namespace NamespaceA
+
+ ' Namespace Scope
+ Sub ScopeA ()
+ sourceFunction = source_function_name
+ sourceNamespace = source_namespace
+ sourceNamespaceRoot = source_namespace_root
+ End Sub
+
+ ' Nested Namespace Scope
+ Namespace NamespaceB.NamespaceC
+
+ Sub ScopeB ()
+ sourceFunction = source_function_name
+ sourceNamespace = source_namespace
+ sourceNamespaceRoot = source_namespace_root
+ End Sub
+
+ End Namespace
+End Namespace
+```
+
+### Transpiled
+```
+Sub ComponentScope()
+ ' Component Scope
+ sourceFunction = "ComponentScope"
+ sourceNamespace = ""
+ sourceNamespaceRoot = ""
+End Sub
+' Namespace Scope
+Sub NamespaceA_ScopeA()
+ sourceFunction = "NamespaceA.ScopeA"
+ sourceNamespace = "NamespaceA"
+ sourceNamespaceRoot = "NamespaceA"
+End Sub
+' Nested Namespace Scope
+Sub NamespaceA_NamespaceB_NamespaceC_ScopeB()
+ sourceFunction = "NamespaceA.NamespaceB.NamespaceC.ScopeB"
+ sourceNamespace = "NamespaceA.NamespaceB.NamespaceC"
+ sourceNamespaceRoot = "NamespaceA"
+End Sub
+```
+
+
+