Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Design principles #2

Closed
helfer opened this issue May 2, 2016 · 0 comments
Closed

Design principles #2

helfer opened this issue May 2, 2016 · 0 comments
Assignees
@helfer
Labels
📝 documentation Focuses on changes to the documentation (docs)

Comments

@helfer
Copy link
Contributor

helfer commented May 2, 2016

We need a doc about design principles for the apollo server

  • What are the guiding principles
  • How is Apollo server it different from GraphQL-JS / express-graphql
  • What features should Apollo server have?
@lorensr lorensr mentioned this issue May 2, 2016
Closed
@zol zol added the 📝 documentation Focuses on changes to the documentation (docs) label May 31, 2016
@helfer helfer mentioned this issue Jun 1, 2016
Closed
@helfer helfer mentioned this issue Jun 3, 2016
Merged
@helfer helfer closed this as completed Jun 29, 2016
DxCx added a commit to DxCx/graphql-server that referenced this issue Jun 12, 2017
@DxCx
fix(graphql-server-core): validation for get queries apollographql#2
ca98504
helfer pushed a commit that referenced this issue Jun 13, 2017
@DxCx @helfer
fix(graphql-server-core): validation for get queries #2
6d26594
abernix added a commit that referenced this issue Jan 25, 2019
@abernix
Merge pull request #2 from apollographql/abernix/plugins
87103cb 
Operation Registry Agent for Apollo Server
abernix added a commit to abernix/apollo-server that referenced this issue Feb 26, 2019
@abernix
Add example application which uses apollo-server-hapi. (apollograph…
09e34a1 
…ql#2)

Much in the same way as this repository has an `apollo-server-express`
example, this brings an example which uses hapi.
trevor-scheer pushed a commit that referenced this issue May 6, 2020
@abernix
Stop using Lerna --exact flag for publishing. (#2)
46ff2fc 
I'm not sure if the `--exact` flag was ever what we wanted.  Specifically,
the `--exact` flag publishes every package without semantic version symbols
in all of its `package.json` dependencies (e.g. prod, dev, optional).

This means that if any package in this repository depends on another
package, all related packages must be republished when a new version of one
package comes out, even if there are no other changes to the others.

This means we're essentially over-publishing.  My hunch is that, at one
point, when we were trying to publish early-access/preview releases of some
packages, we used the `--exact` flag in combination with general
`prerelease` and `--canary` flags and this has remained as a historical
artifact.
trevor-scheer pushed a commit that referenced this issue May 14, 2020
@abernix
Stop using Lerna --exact flag for publishing. (#2)
659d8cd 
I'm not sure if the `--exact` flag was ever what we wanted.  Specifically,
the `--exact` flag publishes every package without semantic version symbols
in all of its `package.json` dependencies (e.g. prod, dev, optional).

This means that if any package in this repository depends on another
package, all related packages must be republished when a new version of one
package comes out, even if there are no other changes to the others.

This means we're essentially over-publishing.  My hunch is that, at one
point, when we were trying to publish early-access/preview releases of some
packages, we used the `--exact` flag in combination with general
`prerelease` and `--canary` flags and this has remained as a historical
artifact.
@glasser glasser mentioned this issue Nov 22, 2022
Closed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@helfer helfer

Labels
📝 documentation Focuses on changes to the documentation (docs)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zol @helfer