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

Formatted CRUD provider typedefs, moved to own file (no functional changes) #3066

Merged
merged 5 commits into from
May 31, 2020

Conversation

Vultraz
Copy link
Contributor

@Vultraz Vultraz commented May 29, 2020

Used single-line comments where applicable and ran each block through prettier with a gql literal attached. Also moved them to a getter helper in a separate file since they're getting really long.

@changeset-bot
Copy link

changeset-bot bot commented May 29, 2020

💥 No Changeset

Latest commit: 2e64001

Merging this PR will not cause any packages to be released. If these changes should not cause updates to packages in this repo, this is fine 🙂

If these changes should be published to npm, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@Vultraz Vultraz changed the title Formatted CRUD provider typedefs (no functional changes) Formatted CRUD provider typedefs, moved to own file (no functional changes) May 29, 2020
@@ -1,6 +1,8 @@
const { GraphQLJSON } = require('graphql-type-json');
const { flatten, objMerge, unique } = require('@keystonejs/utils');

const { _getListCRUDTypes } = require('./listCRUDTypes');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like a weird place for a dangling underscore. Is there a convention we're using that I missed? I've seen us use _method to informally denote "private" API on classes, but it feels weird when used as an export/import

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, not a convention, just a random choice on my part. Removed 👍

Copy link
Contributor

@timleslie timleslie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, very nice 👍

@timleslie timleslie merged commit a2f2430 into keystonejs:master May 31, 2020
@Vultraz Vultraz deleted the formatted-crud-provider branch June 1, 2020 02:25
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.

3 participants