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
{{ message }}
This repository has been archived by the owner on Sep 10, 2019. It is now read-only.
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 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.
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?
The text was updated successfully, but these errors were encountered: