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.

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

Fix #713 #733

Closed
wants to merge 3 commits into from
Closed

Fix #713 #733

wants to merge 3 commits into from

Conversation

antmdvs
Copy link

@antmdvs antmdvs commented Oct 2, 2016

TODO:

  • If this PR is a new feature, reference an issue where a consensus about the design was reached (not necessary for small changes)
  • Make sure all of the significant new logic is covered by tests
  • Rebase your changes on master so that they can be merged easily
  • Make sure all tests and linter rules pass
  • Update CHANGELOG.md with your change
  • Add your name and email to the AUTHORS file (optional)
  • If this was a change that affects the external API, update the docs and post a link to the PR in the discussion

Moved @types packages from devDependencies to dependencies per #713

antmdvs added 3 commits October 2, 2016 17:48
Moved @types packages from devDependencies to dependencies per apollographql#713
Updated AUTHORS & CHANGELOG
@apollo-cla
Copy link

@antmdvs: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

@poloagustin
Copy link
Contributor

I hope this gets merged soon. I'm stuck with these referenced issues 😔

@helfer
Copy link
Contributor

helfer commented Oct 11, 2016

It seems we're between a rock and a hard place here, because adding typings to dependencies makes it impossible to install Apollo Client for people who are behind a firewall and only have access to a restricted set of packages... I'm honestly not sure what the best solution is here.

@poloagustin
Copy link
Contributor

@helfer Sorry, I totally missed that you are explicitly saying you use Typescript in your project. What if we add a Troubleshoot section for now that specifies the @types dependencies for typescript projects.
I also feel that the @types dependencies shouldn't compromise non-Typescript projects.

@helfer
Copy link
Contributor

helfer commented Oct 12, 2016

@poloagustin yeah, I think it would be a great idea to add a "troubleshoot" section to the README. Can you make a PR for that? 🙂

@poloagustin
Copy link
Contributor

sure! 👍

@stubailo
Copy link
Contributor

So should we close this then? And just document the set of types people need to add?

@tuurbo
Copy link

tuurbo commented Oct 13, 2016

There are a lot of types to maintain. Could we have a seperate package, something like apollostack/apollo-client-types or maybe combine them with @types/apollo-client instead of documenting what should be used. Idk how it works, just ideas.

@stubailo
Copy link
Contributor

@tuurbo how do we publish @types/apollo-client? Do we have to go talk to someone to get access to that package name?

@tuurbo
Copy link

tuurbo commented Oct 13, 2016

@DxCx
Copy link
Contributor

DxCx commented Oct 13, 2016

hi @helfer, what about state @types as optionalDependcies.
this was non-typescript users don't need to install them,

@helfer
Copy link
Contributor

helfer commented Oct 13, 2016

@DxCx yeah, maybe that would be a workable solution for now!

@poloagustin
Copy link
Contributor

like this #772 ?

@helfer
Copy link
Contributor

helfer commented Oct 14, 2016

Closing this now, since we merged #772. Let's see where it gets us.

@helfer helfer closed this Oct 14, 2016
@helfer helfer mentioned this pull request Dec 19, 2016
7 tasks
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants