Skip to content

refactor(frontend) :: enable noImplicitAny - #1517

Draft
81reap wants to merge 1 commit into
81reap/ts-11-any-apexchartsfrom
81reap/ts-12-noImplicitAny
Draft

81reap wants to merge 1 commit into
81reap/ts-11-any-apexchartsfrom
81reap/ts-12-noImplicitAny

Conversation

@81reap

@81reap 81reap commented Sep 30, 2026

Copy link
Copy Markdown
Collaborator

noImplicitAny is now enabled.

Most of the remaining implicit workarounds rooted from JSON.parse(data_element.textContent).

This found 3 bugs due to as ChartPoint ::

  1. ChartPoint.x excluded null, z was a number, and y excluded the string[] two value columns return.
  2. ChartSeries.name was a string, and the test pinning a numeric series name has passed all along.
  3. merged_x_values compares x values that may be null, which JavaScript reads as zero.

Most remaining work arounds we should step back and think big about if we need to upstreaming patches along with the fixes.


Stack created with GitHub Stacks CLI • Give Feedback 💬

`noImplicitAny` is now enabled.

Most of the remaining implicit workarounds rooted from `JSON.parse(data_element.textContent)`.

This found 3 bugs due to `as ChartPoint` ::
1. `ChartPoint.x` excluded null, `z` was a number, and `y` excluded the `string[]` two `value` columns return.
2. `ChartSeries.name` was a string, and the test pinning a numeric series name has passed all along.
3. `merged_x_values` compares x values that may be null, which JavaScript reads as zero.

Most remaining work arounds we should step back and think big about if we need to upstreaming patches along with the fixes.
@81reap
81reap added this pull request to stack #1512 September 30, 2026 04:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant