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

bugfix "allspecifications" Pseudogroup showing up. #38

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kaibrockelt
Copy link

What problem is this solving?

The product Context has one Pseudo Group of specifications "allspecifications" that sits along the configured groups. As the name says, it contains ALL specifications again.
The consequence is that in the product comparison table with grouped specifications, any spec listed shows up twice. once in it's corresponding group, and once in the final group "allSpecifications".

The bugfix just adds the condition to skip the allSpecifications item in rendering,

How to test it?

Bugfix applied here:
https://kaibrockelt--ibksport.myvtex.com/bikes?__bindingAddress=ibksport.eu/
Bug visible here:
https://ibksport.myvtex.com/bikes?__bindingAddress=ibksport.eu/

click the little double arrow on 2 products to start comparison. Move to the product-comparison page by clicking compare. See the big fat table at the end? Yep! That is supposed to go after the bugfix,

[Workspace](Link goes here!)

Screenshots or example usage:

allspecs

Describe alternatives you've considered, if any.

No alternatives. its a buggy bug.

Related to / Depends on

acceptance of a PR. nothing else.

How does this PR make you feel? 🔗

@vtex-io-ci-cd
Copy link

vtex-io-ci-cd bot commented Apr 7, 2022

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

@vtex-io-docs-bot
Copy link

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

  • There's nothing new to document 🤔
  • I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

  • I just updated 🎉🎉

@kaibrockelt
Copy link
Author

Im not able to tick the boxes here. No idea why.

so: its a bugfix, so should be a patch
no changes in docs because the app didnt evelove into something new.

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.

1 participant