Comments (3)
I wonder if we could get away with something simpler, and just put this in our getting started guide (and then in the installer once I get to ash_graphql
. Like add a hello_world
and say "this place holder is to give you something working from the outset. Once you have at least one query in one of your resources, you can remove it".
from ash_graphql.
That would certainly be a lot easier to implement!
I think there are probably pros and cons for both ways - if a sample query is added in the app, I can see devs leaving it there, or maybe getting the wrong idea and thinking that you need to add custom queries to interact with resources.
But if it's added dynamically from ash_graphql I can see devs thinking its too much magic, how can I disable/remove it, etc.
I'll leave it up to you when you look at the installer!
from ash_graphql.
This has been implemented by altering the getting started guide. Not as fancy as doing something automatically, but also much easier to do. We can revisit at a later date potentially to do something automatically as well.
from ash_graphql.
Related Issues (20)
- New pagination default not included in upgrade guide HOT 1
- Error when using `paginate_with: nil` and the default `read` action in Ash 3.0 HOT 1
- Allow paginating nested relationships HOT 3
- Error when creating new records with `managed_relationships` in Ash 3.0
- Allow adding a description at the query/mutation level
- An action that `accept`s attributes does not expose those attributes in the schema HOT 1
- Allow JsonString type to be renamed HOT 2
- `require_actor? true` in domain doesn't affect GraphQL mutations HOT 3
- Module does not exists
- Type deduplication quirks
- The mutation/custom read action fails in simple data layer resource HOT 2
- Don't generate empty input objects in AshGraphql HOT 1
- Compilng with latest 1.17 RC throws warnings that cause failure to compile when compiling with warnings as errors
- protocol Enumerable not implemented for nil of type Atom HOT 1
- Filtering by relationship does not work, results in an error HOT 6
- `manual` callback not getting called in the `read_action` of an update mutation HOT 1
- Raised error for `update` mutation, with `read_action` and `Ash.Query.after_action()` HOT 1
- AshGraphql 0.28.1 breaks when resource is in more than one API HOT 2
- Attribute validation escalates to "something went wrong" instead of "invalid attribute" HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ash_graphql.