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 metadata to orders #688

Merged
merged 4 commits into from
Sep 4, 2020
Merged

Add metadata to orders #688

merged 4 commits into from
Sep 4, 2020

Conversation

dominik-zeglen
Copy link
Contributor

I want to merge this change because it adds metadata editor to order view.

PR intended to be tested with API branch: master

Pull Request Checklist

  1. All visible strings are translated with proper context.
  2. All data-formatting is locale-aware (dates, numbers, and so on).
  3. Translated strings are extracted.
  4. Number of API calls is optimized.
  5. The changes are tested.
  6. Data-test are added for new elements.
  7. Type definitions are up to date.
  8. Changes are mentioned in the changelog.

Test environment config

API_URI=https://master.staging.saleor.rocks/graphql/

@patrys
Copy link
Member

patrys commented Sep 3, 2020

Task linked: CU-7pqnkd Add metadata to order views

@github-actions github-actions bot temporarily deployed to metadata-orders September 3, 2020 12:16 Inactive
@@ -235,7 +235,7 @@ export function hasErrors(errorList: UserError[] | null): boolean {
export function getMutationState(
called: boolean,
loading: boolean,
...errorList: UserError[][]
...errorList: any[][]
Copy link
Contributor

Choose a reason for hiding this comment

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

Why any?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well, we only need info how many errors were returned, it's no use for us to know what errors

Copy link
Member

Choose a reason for hiding this comment

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

What do we gain from turning this into any? What if we wanted to explicitly forbid using any tomorrow to get stronger type checking?

Copy link
Member

@krzysztofwolski krzysztofwolski left a comment

Choose a reason for hiding this comment

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

I have the the same question as @orzechdev. Besides that - LGTM

@github-actions github-actions bot temporarily deployed to metadata-orders September 4, 2020 11:06 Inactive
@dominik-zeglen dominik-zeglen merged commit f2a309e into master Sep 4, 2020
@dominik-zeglen dominik-zeglen deleted the metadata/orders branch September 4, 2020 11:12
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.

5 participants