Skip to content
This repository has been archived by the owner on Dec 19, 2019. It is now read-only.

graphQl-914: [Customer] Improve consistency of country field in custo… #958

Merged
merged 5 commits into from Oct 23, 2019

Conversation

kisroman
Copy link
Contributor

…mer address

Description (*)

Fixed Issues (if relevant)

  1. [Customer] Improve consistency of country field in customer address #914

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@@ -28,7 +28,8 @@ input CustomerAddressInput {
city: String @doc(description: "The city or town")
region: CustomerAddressRegionInput @doc(description: "An object containing the region name, region code, and region ID")
postcode: String @doc(description: "The customer's ZIP or postal code")
country_id: CountryCodeEnum @doc(description: "The customer's country")
country_id: CountryCodeEnum @doc(description: "The customer's country") @deprecated(reason: "Use country_code instead.")
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
country_id: CountryCodeEnum @doc(description: "The customer's country") @deprecated(reason: "Use country_code instead.")
country_id: CountryCodeEnum @doc(description: "Deprecated: Use `country_code` instead")

Input types do not support @deprecated directive.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

@m2-community-project m2-community-project bot moved this from Ready for Review to Review in Progress in Pull Request Progress Sep 27, 2019
Copy link
Contributor

@lenaorobei lenaorobei left a comment

Choose a reason for hiding this comment

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

Please pull latest 2.3-develop and address found issues. Thank you.

# Conflicts:
#	app/code/Magento/CustomerGraphQl/etc/schema.graphqls
@magento-engcom-team
Copy link
Contributor

Hi @lenaorobei, thank you for the review.
ENGCOM-6027 has been created to process this Pull Request
✳️ @lenaorobei, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

Copy link
Contributor

@lenaorobei lenaorobei left a comment

Choose a reason for hiding this comment

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

Please see minor issues.

@TomashKhamlai TomashKhamlai added the QA in progress We are checking label Oct 16, 2019
@TomashKhamlai TomashKhamlai added QA passed and removed QA in progress We are checking labels Oct 16, 2019
@magento-engcom-team
Copy link
Contributor

Hi @lenaorobei, thank you for the review.
ENGCOM-6027 has been created to process this Pull Request

@magento-engcom-team magento-engcom-team merged commit 21749cc into magento:2.3-develop Oct 23, 2019
@ghost
Copy link

ghost commented Oct 23, 2019

Hi @kisroman, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@TomashKhamlai
Copy link
Contributor

@lenaorobei is it a milestone 2.3.4?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Development

Successfully merging this pull request may close these issues.

None yet

5 participants