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

[2.3-develop] [ForwardPort] Port of #15020 Update Gallery Template to handle boolean config Variables #15022

Merged
merged 1 commit into from
May 9, 2018

Conversation

gwharton
Copy link
Contributor

@gwharton gwharton commented May 5, 2018

Description

Changes implemented in the resolution to #12285, boolean configuration variables are now properly typed booleans, instead of the strings "true" and "false". This fix was applied to 2.2-develop only. Pull request #15021 applies the fix to 2.3-develop, hence this is now required in 2.3-develop aswell.

If we don't apply PR #15021 and this PR to 2.3-develop, then 2.2 and 2.3 will become horribly out of sync.

Fixed Issues (if relevant)

  1. [2.2.4] Gallery theme variables being ignored #15009: 2.2.4 Gallery theme variables being ignored

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

… handle boolean config Variables

Due to changes implemented in the resolution to #12285, boolean configuration variables are now properly typed booleans, instead of the strings "true" and "false".

Without this fix applied, config vals that were true were being output in the gallery template javascript as : 1 and values that were false were being output as :

This causes javascript errors for any item that is set to false.
@VladimirZaets
Copy link
Contributor

Hi, @gwharton , I took your PR into processing, thank you for collaboration.

@magento-engcom-team
Copy link
Contributor

Hi @gwharton. Thank you for your contribution.
Changes from your Pull Request will be available with the upcoming 2.3.0 release.

@gwharton gwharton deleted the 2.3-develop-15020 branch May 9, 2018 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants