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
To provide the best experience for consumers of EUI, including those who consume from TypeScript projects, we need to provide quality TS definitions. To date we have been writing .d.ts files and hand-matching exports and component definitions. This is time consuming, often forgotten, and does not guarantee the definitions match actual code (proptypes or other usage) - in fact we have already had bug fixes to address these inconsistencies. To solve these issues we want to support authoring EUI components & other code in TypeScript.
Requirements
lint TypeScript code (currently the .d.ts files are linted, but with a subset of the rules)
Expanding the conversation from #256
To provide the best experience for consumers of EUI, including those who consume from TypeScript projects, we need to provide quality TS definitions. To date we have been writing
.d.ts
files and hand-matching exports and component definitions. This is time consuming, often forgotten, and does not guarantee the definitions match actual code (proptypes or other usage) - in fact we have already had bug fixes to address these inconsistencies. To solve these issues we want to support authoring EUI components & other code in TypeScript.Requirements
.d.ts
files are linted, but with a subset of the rules)types
directory for publishing ( TS types output #1304 )The text was updated successfully, but these errors were encountered: