Skip to content
This repository has been archived by the owner on Mar 21, 2023. It is now read-only.

Migrate to TypeScript #199

Open
tofumatt opened this issue Mar 8, 2020 · 0 comments · May be fixed by #221
Open

Migrate to TypeScript #199

tofumatt opened this issue Mar 8, 2020 · 0 comments · May be fixed by #221
Assignees
@tofumatt
Labels
code quality gotta shave those yaks! documentation
Milestone
Future

Comments

@tofumatt
Copy link
Member

tofumatt commented Mar 8, 2020

Let's explore how @sarahmonster finds it in other projects, but given we will likely want to export types and this is a component library, building with TypeScript could be beneficial for development and also for consumers of the library—including our own apps!

This isn't at all important and it's best to wait until we try a TypeScript project first to decide on this.
@tofumatt tofumatt added code quality gotta shave those yaks! documentation labels Mar 8, 2020
@tofumatt tofumatt self-assigned this Mar 8, 2020
@tofumatt tofumatt changed the title Consider migrating to TypeScript Migrate to TypeScript Mar 8, 2020
@tofumatt tofumatt added this to the Future milestone Mar 8, 2020
This was referenced Mar 23, 2020
Closed
Merged
tofumatt added a commit that referenced this issue Apr 18, 2020
@tofumatt
feat: Move to TypeScript
74c4d31 
Closes #199
@tofumatt tofumatt linked a pull request Apr 18, 2020 that will close this issue
Draft
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@tofumatt tofumatt

Labels
code quality gotta shave those yaks! documentation
Projects
None yet
Milestone
Future
Development

Successfully merging a pull request may close this issue.

feat: Move to TypeScript octopusthink/nautilus
1 participant
@tofumatt