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 Jul 27, 2020. It is now read-only.
When you're working in a team, it's really good to have a common practice. What's is the best practices/patterns for Yoga2 or GraphQL Nexus for that matter, everything in programming have dos and donts
The text was updated successfully, but these errors were encountered:
guledali
changed the title
Add a official styleguide for Yoga2 in the docs
[Development guidelines] Add a official styleguide for Yoga2 in the docs
Apr 17, 2019
guledali
changed the title
[Development guidelines] Add a official styleguide for Yoga2 in the docs
[Development Guidelines] Add a official styleguide for Yoga2 in the docs
Apr 17, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When you're working in a team, it's really good to have a common practice. What's is the best practices/patterns for Yoga2 or GraphQL Nexus for that matter, everything in programming have dos and donts
Having a styleguide similar to https://vuejs.org/v2/style-guide/ or https://learn-vuejs.github.io/vue-patterns/patterns/ will make on boarding easier and more appealing for large teams as well.
One example would be looking at
Gitlab GraphQL API Styleguide
The text was updated successfully, but these errors were encountered: