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

bug where attribute reporting dissapears #1514

Merged
merged 5 commits into from
Feb 3, 2025

Conversation

paulr34
Copy link
Collaborator

@paulr34 paulr34 commented Jan 29, 2025

No description provided.

@paulr34 paulr34 changed the title bug where attribute reporting disapears, need to ensure it waits bug where attribute reporting disapears - no need to call the same function again Jan 30, 2025
@paulr34 paulr34 changed the title bug where attribute reporting disapears - no need to call the same function again bug where attribute reporting dissapears - no need to call the same function again Jan 30, 2025
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.56%. Comparing base (30f9298) to head (215852c).
Report is 31 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1514      +/-   ##
==========================================
- Coverage   66.76%   66.56%   -0.20%     
==========================================
  Files         193      194       +1     
  Lines       20999    21707     +708     
  Branches     4614     4798     +184     
==========================================
+ Hits        14020    14450     +430     
- Misses       6979     7257     +278     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

listType === 'selectedAttributes' &&
attributeData.isReportable
) {
editContext.listType = 'selectedReporting'
Copy link
Collaborator

Choose a reason for hiding this comment

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

What does editContext.listType = 'selectedReporting' do?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It identifies the list type

Copy link
Collaborator

Choose a reason for hiding this comment

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

if ( addedValue && listType === 'selectedAttributes' && attributeData.isReportable ) { editContext.listType = 'selectedReporting' } this.$store.dispatch('zap/updateSelectedAttribute', editContext)

Will be safer to do this. Getting rid of that line can cause issues if unsure of its removal.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

it breaks because both dispatch collide with each other
I think you're right.

@ethanzhouyc ethanzhouyc self-requested a review February 3, 2025 16:39
listType === 'selectedAttributes' &&
attributeData.isReportable
) {
editContext.listType = 'selectedReporting'
Copy link
Collaborator

Choose a reason for hiding this comment

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

if ( addedValue && listType === 'selectedAttributes' && attributeData.isReportable ) { editContext.listType = 'selectedReporting' } this.$store.dispatch('zap/updateSelectedAttribute', editContext)

Will be safer to do this. Getting rid of that line can cause issues if unsure of its removal.

@paulr34 paulr34 changed the title bug where attribute reporting dissapears - no need to call the same function again bug where attribute reporting dissapears Feb 3, 2025
@paulr34 paulr34 merged commit e8470e5 into project-chip:master Feb 3, 2025
14 checks passed
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