Skip to content

Conversation

amenk
Copy link
Contributor

@amenk amenk commented Dec 22, 2022

See the issues #14495 for details

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Customer export not work with custom attribute #14495

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
  • [no] All new or changed code is covered with unit/integration tests (if applicable)
  • [no] README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • [t.b.d] All automated tests passed successfully (all builds are green)

* As described in the issue, it does not make sense to use the backend-type for the UI-component data type, because those do not exist necessarily
* Changed it to frontend_input
@m2-assistant
Copy link

m2-assistant bot commented Dec 22, 2022

Hi @amenk. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@amenk
Copy link
Contributor Author

amenk commented Dec 23, 2022

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@swnsma swnsma self-requested a review December 24, 2022 12:57
@swnsma
Copy link
Contributor

swnsma commented Dec 24, 2022

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

Copy link
Contributor

@swnsma swnsma left a comment

Choose a reason for hiding this comment

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

Hi @amenk,
Thank you for your contribution!

Could you please check failed test, seems it may have relation to functionality you are changing.

@amenk
Copy link
Contributor Author

amenk commented Dec 25, 2022

Failing test:

public function testPrepareWithUpdateColumn(): void

@amenk
Copy link
Contributor Author

amenk commented Dec 25, 2022

@magento run Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@amenk
Copy link
Contributor Author

amenk commented Dec 25, 2022

Unit test are green now
@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@amenk
Copy link
Contributor Author

amenk commented Dec 25, 2022

@magento run Functional Tests CE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@swnsma
Copy link
Contributor

swnsma commented Dec 26, 2022

@magento run Functional Tests B2B,Functional Tests CE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@swnsma
Copy link
Contributor

swnsma commented Dec 26, 2022

@magento run Functional Tests B2B

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Hotel engcom-Hotel added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Dec 27, 2022
@engcom-Lima engcom-Lima added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Dec 27, 2022
@engcom-Echo engcom-Echo self-assigned this Jan 20, 2023
@engcom-Echo
Copy link
Contributor

@amenk @swnsma
Thanks for the collaboration & contribution!

✔️ QA Passed
fix: #14495 Allow custom varchar attributes for customer grid

Manual Scenario Steps
Steps to Reproduce

  1. Add new customer attribute whose code is varchar_attribute, Input Type => Text Field, Add to Column Options => Yes, Use in Filter Options => Yes.
  2. Define the varchar_attribute in the customer_listing.xml in sample module
  3. Flush cache and reindex
  4. Export the customer data at the Customer listing page.

Before: ✖️
image

After: ✔️
Able to export customers.
image

Hence moving to Merge In Progress

@engcom-Charlie
Copy link
Contributor

It seems bot moved this PR from Merge in Progress to Ready for Testing hence moving it back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Status: Recently Merged
Development

Successfully merging this pull request may close these issues.

Customer export not work with custom attribute
7 participants