-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Mview patch update 41 v 4 #30129
Mview patch update 41 v 4 #30129
Conversation
-- move framework logic to saas-export
-- move framework logic to saas-export
-- move framework logic to saas-export
-- move framework logic to saas-export
-- move framework logic to saas-export
Hi @skovalenk. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. 🕙 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, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
--create a test for this
--create a test for this
--create a test for this
@@ -11,6 +11,11 @@ | |||
*/ | |||
interface ChangelogInterface | |||
{ | |||
const ATTRIBUTE_SCOPE_SUPPORT = 'attribute_scope'; | |||
const STORE_SCOPE_SUPPORT = 'store_scope'; | |||
const ATTRIBUTE_COLUMN = 'attribute_id'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be defined in eav module?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also visibility should be provided whether it's reusable const and a part of API (public
) or part of the implementation (protected
/ private
).
const ATTRIBUTE_SCOPE_SUPPORT = 'attribute_scope'; | ||
const STORE_SCOPE_SUPPORT = 'store_scope'; | ||
const ATTRIBUTE_COLUMN = 'attribute_id'; | ||
const STORE_COLUMN = 'store_id'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be defined in store module?
Hi @skovalenk, thank you for your contribution! |
Description (*)
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)