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

Add option to keep schema enum order for code generating #2043

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

viico
Copy link

@viico viico commented Jul 17, 2020

Hi,

This is a PR related to issue #1760. We want to can keep schema enum order when generating code and not sort them alphabetically. This PR keep sort by default but add an option to don't.

I added a test and I update only for typescript generation. I don't know if it could be interesting for another generation.

TODO:

  • Update CHANGELOG.md* with your change (include reference to issue & this PR)
  • 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

*Make sure changelog entries note which project(s) has been affected. See older entries for examples on what this looks like.

@apollo-cla
Copy link

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

@viico
Copy link
Author

viico commented Jul 31, 2020

I fixed unit tests but "ci/circleci: NodeJS 10" still failing, I don't see why.

@cdaz5
Copy link

cdaz5 commented Apr 16, 2021

this bug has been a thorn in our side for a while now ... anything i can do to help push this merge along? happy to help just LMK

@RebMeir
Copy link

RebMeir commented Nov 23, 2021

We also faced the same problem.. anything we can do to push it?

@viico viico force-pushed the keepSchemaEnumOrder branch from 59a8c7d to ad0ee7e Compare November 28, 2021 11:40
@StasKeiss
Copy link

Can this be pushed to the main branch? This bug is really a big issue for us.

@Shirane85
Copy link

Shirane85 commented Dec 15, 2021

This is a major issue. We now need to create duplicates of the enums in order to support the existing code of the client. This is terrible.

@SamuelEls
Copy link

Is this completely forgotten feature?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants