Making compute focused updates to the Application documentation #166
Conversation
There was a problem hiding this comment.
There is a ton of fantastic content in here. We should use it.
However, I still believe that for introducing users to Harper, we should prioritize showing the simplest and easiest path from installation to writing data and querying it so they can so how easily they can get started. They shouldn't have to write JavaScript before they can do a simple query, and the introduction should help users to see the powerful OOTB functionality before they start trying to customize it.
But after that, I think this provides tons of great examples of how to config files are structured, how that works, and how to build custom endpoints.
Including @nenharper as well here because this page is really the main content for the future getting started guide.
|
|
||
| ```graphql | ||
| type Dog @table { | ||
| # properties will go here soon | ||
| type Dogs @table { |
There was a problem hiding this comment.
My understanding is that it is the Harper standard to use singular names for tables, not plural (I didn't define that standard, just followed it).
|
|
||
| ## Adding an Endpoint | ||
| ## Adding a Endpoint with REST |
No description provided.