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

fix/1601 incorrect productinfo #1610

Merged
merged 3 commits into from
Aug 21, 2018
Merged

fix/1601 incorrect productinfo #1610

merged 3 commits into from
Aug 21, 2018

Conversation

vue-kacper
Copy link
Contributor

Related issues

#1601

Short description and why it's useful

Introduced computed properies instead of non-reactive data() properies. Fixed issue with custom product attributes have not been updated correctly when navigating from one product page directly to another product page.

@pkarw Solution propsed by you doesn't work so I decided to use different approach

@vue-kacper vue-kacper changed the title fix/#1601 fix/1601 incorrect productinfo Aug 20, 2018
Copy link
Collaborator

@pkarw pkarw left a comment

Choose a reason for hiding this comment

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

Thanks Kacper this is far better approach - probably to be used for the related products as well (?) Can You just check the review note I’ve put on logic duplication in the *.vue theme component?

})
if (option) {
results.push(option.label)
computed: {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Shouldn’t this logic be just in the core? I’m not sure but I think it’s duplicated in the *.vue component is kind of DRY principle violation.
Shouldn’t it be just left in the core?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You are absolutelty right, It was originally duplicated - to make sure I'll compare both files and remove duplicated logic if there are no differences.

@vue-kacper
Copy link
Contributor Author

@pkarw Done, I'll check other places where we can use computed properties instead of firing events for proper reactivity working and create another PR if necessary.

@pkarw pkarw merged commit 7981246 into vuestorefront:develop Aug 21, 2018
@pkarw
Copy link
Collaborator

pkarw commented Aug 21, 2018

Thanks!

@pkarw pkarw added this to the 1.3 milestone Aug 21, 2018
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.

2 participants