-
Notifications
You must be signed in to change notification settings - Fork 21
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
Issue 24 #28
Issue 24 #28
Conversation
- add state fix for console command - add command option resolving fix - add shipments aggregator - add shipments count aggregator unit tests coverage.
- add categories count aggregator based on category status, category menu status and store code - add unit tests coverage for categories count aggregator.
- adjust 'magento_store_count_total' metric; - add status label to stores count; - adjust unit tests coverage;
- Add magento_website_count_total metric. - add unit tests coverage.
- Update readme.md file.
- Fix code styles.
- Fix code styles.
I believe it does not make sense to fix alignments, as difference in PHP Storm settings. |
{ | ||
private const METRIC_CODE = 'magento_catalog_category_count_total'; | ||
private const T_ATT = 'm2_eav_attribute'; | ||
private const T_CAT_ENT_INT = 'm2_catalog_category_entity_int'; |
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.
What are these abbreviations? Test? Table? I'd suggest to be more explicit here.
Hi @swnsma, thank you for the PR. I am gonna look at the CI stuff next week. I guess it is time to check out the Github Actions :D. Besides that, your code looks fine. I don't actually like these crazy big SQL's but I guess we have to use them in order to be as performant as possible. Will try the metrics and give feedback next as well |
Fix code review notices.
Related ticket:
#24
Metrics added:
Metrics changed:
Adjusted unit tests coverage.
Updated README.md
Points to discuss:
Possible suggestions:
menu_status
label and collect only category statusmenu_status
if category is disabled (= leave only 3 metrics, if category disabled - consider that it won't be showed in the menu).It will require separated SQL query to fetch data for admin store (e.g. all available categories). Should we collect this data too, or only leave data collection per actual store?