Merge branch 'master' of https://github.com/rokucommunity/bslint into…

… bsc-0.67.0

CHANGELOG.md

@@ -6,6 +6,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 
 
+## [0.8.22](https://github.com/rokucommunity/bslint/compare/v0.8.21...0.8.22) - 2024-07-24
+### Changed
+ - add rule to prevent use of `assocarray` and `array` component fields in xml ([#115](https://github.com/rokucommunity/bslint/pull/115))
+ - upgrade to [[email protected]](https://github.com/rokucommunity/brighterscript/blob/master/CHANGELOG.md#0674---2024-07-24). Notable changes since 0.67.1:
+     - Fix crash with missing scope ([brighterscript#1234](https://github.com/rokucommunity/brighterscript/pull/1234))
+     - fix: conform bsconfig.schema.json to strict types ([brighterscript#1205](https://github.com/rokucommunity/brighterscript/pull/1205))
+     - Flag using devDependency in production code ([brighterscript#1222](https://github.com/rokucommunity/brighterscript/pull/1222))
+
+
+
+## [0.8.21](https://github.com/rokucommunity/bslint/compare/v0.8.20...v0.8.21) - 2024-05-17
+### Changed
+ - fix node14 ([#106](https://github.com/rokucommunity/bslint/pull/106))
+ - upgrade to [[email protected]](https://github.com/rokucommunity/brighterscript/blob/master/CHANGELOG.md#0671---2024-05-16). Notable changes since 0.65.27:
+     - Fix crash when diagnostic is missing range ([brighterscript#1174](https://github.com/rokucommunity/brighterscript/pull/1174))
+     - Move function calls to separate diagnostic ([brighterscript#1169](https://github.com/rokucommunity/brighterscript/pull/1169))
+     - resolve the stagingDir option relative to the bsconfig.json file ([brighterscript#1148](https://github.com/rokucommunity/brighterscript/pull/1148))
+     - Upgrade to @rokucommunity/logger ([brighterscript#1137](https://github.com/rokucommunity/brighterscript/pull/1137))
+
+
+
 ## [0.8.20](https://github.com/rokucommunity/bslint/compare/v0.8.19...v0.8.20) - 2024-03-27
 ### Changed
  - upgrade to [[email protected]](https://github.com/rokucommunity/brighterscript/blob/master/CHANGELOG.md#06527---2024-03-27). Notable changes since 0.65.25:

README.md

@@ -161,7 +161,11 @@ Default rules:
         "unreachable-code": "info",
         "case-sensitivity": "warn",
         "unused-variable": "warn",
-        "consistent-return": "error"
+        "consistent-return": "error",
+
+        "no-assocarray-component-field-type": "off",
+        "no-array-component-field-type": "off",
+        "no-regex-duplicates": "off"
     }
 }
 ```
@@ -248,6 +252,12 @@ Default rules:
     - `always`: ensures all white and black color-format values either match or are darker/ lighter than the minimum recommended values. For white the maximum value is `#EBEBEB` and for black the minimum value is `#161616`
     - `off`: do not validate (**default**)
 
+-   `no-assocarray-component-field-type`: Using 'assocarray' type in component markup can result in inefficient copying of data during transfer to the render thread. Use 'node' field types for more efficient transfer of data between component boundaries by avoiding expensive data cloning (`error | warn | info | off`)
+
+-   `no-array-component-field-type`: Using 'array' type in component markup can result in inefficient copying of data during transfer to the render thread. Use 'node' field types for more efficient transfer of data between component boundaries by avoiding expensive data cloning(`error | warn | info | off`)
+
+-   `no-regex-duplicates`: Avoid creating multiple roRegex objects with the same pattern as it leads to less performant code. (`error | warn | info | off`)
+
 ### Strictness rules
 
 - `type-annotations`: validation of presence of `as` type annotations, for function
@@ -325,4 +335,4 @@ Running `bslint` with `--checkUsage` parameter will attempt to identify unused c
 - Any script/component not walked will produce a warning.
 
 ## Changelog
-Click [here](CHANGELOG.md) to view the changelog
+Click [here](CHANGELOG.md) to view the changelog