[New Feature] Tests for JS based components

[kotAPI]

🚀 Feature Request

---

Feature Description

When we write tests in test.tsx files, we are unable to test our components to its fullest as they error out.

We should probably write tests for JS and TS based projects separately

[GoldGroove06]

Example of tests in text component (TSX)

[chromium-52]

@kotAPI @GoldGroove06 Is this still an issue? TS code that should be an error can be silenced using @ts-expect-error (e..g.

ui/src/components/ui/Tooltip/tests/Tooltip.test.tsx

Line 45 in 2d9fbca

// @ts-expect-error: label should be a string

)

Example of tests in text component (TSX)

I think this is actually a JSX syntax error (as= 0 should be as={0}), not a TS error

[GoldGroove06]

Me and @kotAPI are not experts in ts

[chromium-52]

Could you try adding this between lines 71 and 72: // @ts-expect-error? @ts-expect-error is a special comment in TS that suppresses expected TS errors on the line directly below it (I think it's a good idea to also describe what the actual expected error is after the @ts-expect-error)

I'm also noticing that the type of the as prop is a string but based on the tests on lines 76 and 81, the values for this prop can be an array or a boolean as well. We should update the type of the as prop in <Text /> to take this into account

[GoldGroove06]

Could you try adding this between lines 71 and 72: // @ts-expect-error? @ts-expect-error is a special comment in TS that suppresses expected TS errors on the line directly below it (I think it's a good idea to also describe what the actual expected error is after the @ts-expect-error)

Thanks for recommending

I'm also noticing that the type of the as prop is a string but based on the tests on lines 76 and 81, the values for this prop can be an array or a boolean as well. We should update the type of the as prop in <Text /> to take this into account

We are testing invalid edge cases for as

[kotAPI]

Could you try adding this between lines 71 and 72: // @ts-expect-error? @ts-expect-error is a special comment in TS that suppresses expected TS errors on the line directly below it (I think it's a good idea to also describe what the actual expected error is after the @ts-expect-error)

I'm also noticing that the type of the as prop is a string but based on the tests on lines 76 and 81, the values for this prop can be an array or a boolean as well. We should update the type of the as prop in <Text /> to take this into account

This is actually a good idea! Thanks bud