Skip to content
This repository has been archived by the owner on Sep 10, 2019. It is now read-only.

Move to Typescript #8

Open
jlengstorf opened this issue Nov 20, 2017 · 3 comments
Open

Move to Typescript #8

jlengstorf opened this issue Nov 20, 2017 · 3 comments

Comments

@jlengstorf
Copy link
Member

A discussion with @schickling suggested the use of Typescript, since the majority of the GraphQL tooling ecosystem is written in Typescript.

I'm on board with this for the core of GrAMPS, but want to make sure that data sources don't require Typescript. (Doing so would be a huge onboarding problem within my team; it's not possible to just proclaim, "Okay, everyone needs to learn Typescript now!")

@corycook, you've got Typescript experience, right?

@schickling
Copy link

I'm on board with this for the core of GrAMPS, but want to make sure that data sources don't require Typescript.

Can confirm this. No problem at all.

@corycook
Copy link

Yeah, I can work on this.

@jlengstorf
Copy link
Member Author

@corycook Awesome, thanks! Let's finalize the core features for 1.0 and then we can start the conversion while we build it. I'll start a new issue with a 1.0 checklist so we can make sure everyone's on the same page.

@jlengstorf jlengstorf mentioned this issue Nov 21, 2017
5 tasks
@jlengstorf jlengstorf changed the title [1.0] Move to Typescript Move to Typescript Dec 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants