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

Vine patch 1 #533

Closed
wants to merge 2 commits into from
Closed

Vine patch 1 #533

wants to merge 2 commits into from

Conversation

dvm1984
Copy link
Contributor

@dvm1984 dvm1984 commented Jul 27, 2023

What is the purpose of this pull request?

<added neighborhood to the GAPI-generated address at checkout.

What problem is this solving?

The suburb is mandatory in New Zealand. By adding it to the address format display, it solves a client request.

How should this be manually tested?

Clone the repo to VSCODE, login to localtest--vineoneline.myvtex.com, add the changes to the NZL.ts country file and change the manifest json app version, then link the app to the workspace. Proceed with placing an order and choose an address, for example 1020 .... (google maps auto-fill will do the rest). Notice the suburb is showing.

Client is live, do not attempt this on the master workspace please.

Screenshots or example usage

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Requires change to documentation, which has been updated accordingly.

updating the way GAPI auto-filled address is displayed at checkout. Client needs the neighborhood to show.
@dvm1984 dvm1984 requested a review from a team as a code owner July 27, 2023 01:12
@vtex-io-ci-cd
Copy link
Contributor

vtex-io-ci-cd bot commented Jul 27, 2023

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

@jeffersontuc
Copy link
Contributor

It seems it was already implemented by another PR

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.

4 participants