You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposal: Adding support for Typescript-based Tonic component examples
Context
Our teams in Canada are developing web applications primarily using Typescript for writing React components. These components are based on Tonic UI components but enhanced with Typescript's type checking. This approach has been in place for some time, and various teams are either building new web applications or contributing to existing ones that use Typescript. As our experience with integrating Typescript and Tonic components has grown, so has the need for well-documented examples of common components like Menus, Inputs, Modals, and Tables that adhere to these patterns and practices.
Proposal
Allow for addition of Typescript-based Tonic component examples to the Tonic repository, similar to the existing JavaScript examples. These examples should be referenced within the existing v2+ documentation.
The text was updated successfully, but these errors were encountered:
Proposal: Adding support for Typescript-based Tonic component examples
Context
Our teams in Canada are developing web applications primarily using Typescript for writing React components. These components are based on Tonic UI components but enhanced with Typescript's type checking. This approach has been in place for some time, and various teams are either building new web applications or contributing to existing ones that use Typescript. As our experience with integrating Typescript and Tonic components has grown, so has the need for well-documented examples of common components like Menus, Inputs, Modals, and Tables that adhere to these patterns and practices.
Proposal
Allow for addition of Typescript-based Tonic component examples to the Tonic repository, similar to the existing JavaScript examples. These examples should be referenced within the existing v2+ documentation.
The text was updated successfully, but these errors were encountered: