Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / yamalight/graffiti issues and pull requests
#13 - Do we have to create custom resolvers for arrays of ObjectID's in order to get subfield access in graphql?
Issue -
State: closed - Opened by Cigoler over 3 years ago
- 4 comments
Labels: question
#12 - CORS plugin
Issue -
State: open - Opened by yamalight almost 4 years ago
- 1 comment
Labels: enhancement
#11 - Is the module fully transpiled?
Issue -
State: closed - Opened by bahmutov almost 4 years ago
- 7 comments
#10 - Feature request: Configurable schemas folder name
Issue -
State: closed - Opened by chaeron about 4 years ago
- 4 comments
Labels: enhancement, good first issue, core
#9 - Next.js, React and React-DOM should be peer deps
Issue -
State: closed - Opened by yamalight about 4 years ago
Labels: enhancement, good first issue, plugin-next
#8 - Release v1.0
Issue -
State: closed - Opened by yamalight about 4 years ago
#7 - Development mode
Issue -
State: closed - Opened by yamalight about 4 years ago
#6 - Better npm deploys
Issue -
State: closed - Opened by yamalight about 4 years ago
#5 - Add tests, linting, CI
Issue -
State: closed - Opened by yamalight about 4 years ago
#4 - Production-ready deployment
Issue -
State: closed - Opened by yamalight about 4 years ago
#3 - Support for custom resolvers and GraphQL methods
Issue -
State: closed - Opened by yamalight about 4 years ago
#2 - Add way to change / remove default GraphQL methods
Issue -
State: closed - Opened by yamalight about 4 years ago
#1 - Implement plugins support
Issue -
State: closed - Opened by yamalight about 4 years ago
- 1 comment