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

Sitemap filename can't exceed 32 characters #13937 #20044

Conversation

irajneeshgupta
Copy link
Member

@irajneeshgupta irajneeshgupta commented Jan 2, 2019

Description (*)

The Sitemap filename length validation was not added , hence added \Magento\Framework\Validator\StringLength max 32 length validation for sitemap filename and it will not trim filename exceeding 32 chars. Client side validation in filename field of form is also added to fix this issue 'validate-length maximum-length-32'. Updated saveTest unit test case.

Fixed Issues (if relevant)

  1. magento/magento2#Sitemap filename can't exceed 32 characters #13937: Issue title : Sitemap filename can't exceed 32 characters

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)

@magento-engcom-team
Copy link
Contributor

Hi @irajneeshgupta. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento-engcom-team give me test instance - deploy test instance based on PR changes
  • @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@miguelbalparda
Copy link
Contributor

Using the objectmanager doesn't seem to be the best path here, care to recheck?

@irajneeshgupta
Copy link
Member Author

irajneeshgupta commented Jan 2, 2019

Using the objectmanager doesn't seem to be the best path here, care to recheck?

@miguelbalparda
yeah but Magento itself used objectmanager the same in above lines for path validation , hence i added it in the same way.
I will recheck it and amend my commit.
Thanks for your suggestion.

@irajneeshgupta
Copy link
Member Author

irajneeshgupta commented Jan 3, 2019

Using the objectmanager doesn't seem to be the best path here, care to recheck?

@miguelbalparda
I rechecked and removed objectManager from last commit.
Thank you.

@irajneeshgupta
Copy link
Member Author

@miguelbalparda can you please review changes.
Thanks.

@magento-engcom-team
Copy link
Contributor

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

Copy link
Member

@sivaschenko sivaschenko left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution @irajneeshgupta , please see my code review notes.

/**
* @var $_stringValidator
*/
public $_stringValidator;
Copy link
Member

Choose a reason for hiding this comment

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

Please change properties access level to private and remove the underscore prefix from property names

Copy link
Member Author

Choose a reason for hiding this comment

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

Okay , I will made these changes.

* @param \Magento\Sitemap\Model\SitemapFactory $sitemapFactory
*/
public function __construct(
\Magento\Backend\App\Action\Context $context,
Copy link
Member

Choose a reason for hiding this comment

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

Please add dependencies in a backward compatible way, see "Adding a constructor parameter" section of Backward compatible development guide for details

Copy link
Member Author

Choose a reason for hiding this comment

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

okay I will update it.

const MAX_FILENAME_LENGTH = 32;

/**
* @var $_stringValidator
Copy link
Member

Choose a reason for hiding this comment

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

Please correct propeties' types in phpdocs

Copy link
Member Author

@irajneeshgupta irajneeshgupta Jan 21, 2019

Choose a reason for hiding this comment

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

okay I will make these changes

/**
* @var \Magento\Framework\Validator\StringLength|\PHPUnit_Framework_MockObject_MockObject
*/
protected $lengthValidator;
Copy link
Member

Choose a reason for hiding this comment

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

it's preferable to declare properties as private unless they are used by child classes

Copy link
Member Author

Choose a reason for hiding this comment

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

okay sure

@irajneeshgupta
Copy link
Member Author

@sivaschenko

I have made changes that you recommended.
Please review.

Thanks.

@magento-engcom-team
Copy link
Contributor

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

@irajneeshgupta
Copy link
Member Author

@sivaschenko
any updates on this PR.

@sivaschenko
Copy link
Member

Hi @irajneeshgupta thanks for your fixes, the pull request is being processed internally.

@ghost
Copy link

ghost commented Mar 1, 2019

Hi @irajneeshgupta, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

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.

8 participants