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 Apr 23, 2022. It is now read-only.
It seems like there are ways to do this with pre-processing, which feel a bit weird, but which also seem to be workable. Allows us to get a single source of truth between frontend and backend types. There are potentially better options as TS and GraphQL are both continually evolving- more research needed.
If we do end up being able to compile the existing backend with AssemblyScript some day, it means we'll be able to share type information and base classes between the frontend and backend of the system, increasing code comprehension dramatically.
Even if we don't end up using any GFD code on the rusty-chain version, we can potentially get a head start on declaring the type system for integration with the Apollo / GraphQL view layer, which is an important aspect of authoring error-free UI code.
Either way, seems a win-win to attempt merging these two parts of the codebase.
The text was updated successfully, but these errors were encountered:
pospi
changed the title
Investigate binding backend types to GraphQL API objects
Attain single source of truth between GraphQL schema and TypeScript types
Jan 16, 2019
It seems like there are ways to do this with pre-processing, which feel a bit weird, but which also seem to be workable. Allows us to get a single source of truth between frontend and backend types. There are potentially better options as TS and GraphQL are both continually evolving- more research needed.
If we do end up being able to compile the existing backend with
AssemblyScript
some day, it means we'll be able to share type information and base classes between the frontend and backend of the system, increasing code comprehension dramatically.Even if we don't end up using any GFD code on the rusty-chain version, we can potentially get a head start on declaring the type system for integration with the Apollo / GraphQL view layer, which is an important aspect of authoring error-free UI code.
Either way, seems a win-win to attempt merging these two parts of the codebase.
The text was updated successfully, but these errors were encountered: