Skip to content

Conversation

@quisse
Copy link

@quisse quisse commented Apr 4, 2018

View.xml is inheriting image sizes from parent (so an optional field is replaced by the value of parent)

  • Made media attributes nullable and parse them correct

Description

Fixed Issues (if relevant)

  1. View.xml is inheriting image sizes from parent (so an optional field is replaced by the value of parent) #12250: View.xml is inheriting image sizes from parent (so an optional field is replaced by the value of parent)

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)

@sidolov
Copy link
Contributor

sidolov commented Apr 5, 2018

Hi @quisse , described behavior is expected, nodes in view.xml file will be overwritten by parent theme if they wasn't defined. For your case with image tag for overriding height field you may define empty height tag, in that case parent height will be ignored. Proposed changes are backward incompatible and may affect all existing themes.

@quisse
Copy link
Author

quisse commented Apr 5, 2018

Hi @sidolov, ok i understand. Now I've made it possible to add nulllable attributes.

@quisse quisse requested a review from ishakhsuvarov April 18, 2018 09:20
@ishakhsuvarov ishakhsuvarov requested a review from sidolov April 18, 2018 09:26
@quisse quisse added this to the April 2018 milestone Apr 27, 2018
@quisse
Copy link
Author

quisse commented May 16, 2018

Any update on this, @sidolov?

@okorshenko okorshenko modified the milestones: April 2018, May 2018 May 18, 2018
Copy link
Contributor

@sidolov sidolov left a comment

Choose a reason for hiding this comment

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

Hi @quisse , fix looks good for me, but I think it would be better review all properties from view.xsd and make nillable all elements that make sense for override in 3d party extensions

@okorshenko okorshenko removed this from the May 2018 milestone May 31, 2018
@quisse
Copy link
Author

quisse commented Jun 19, 2018

I've refactored for more nillable attributes and to me it looks like that's all. Do you agree? If not can you please suggest others?

@quisse
Copy link
Author

quisse commented Jul 4, 2018

@sidolov ?

@magento-engcom-team
Copy link
Contributor

Hi @sidolov, thank you for the review.
ENGCOM-2650 has been created to process this Pull Request

@magento-engcom-team
Copy link
Contributor

Hi @quisse. Thank you for your contribution.
We will aim to release these changes as part of 2.2.7.
Please check the release notes for final confirmation.

Please, consider to port this solution to 2.3 release line.
You may use Porting tool to port commits automatically.

@quisse
Copy link
Author

quisse commented Aug 8, 2018

Already implemented in 2.3 by magento-architects/MAGETWO-91314-validate-new

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.

6 participants