Skip to content

Fixed spelling and adjusted white spaces #26048

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

Merged
merged 6 commits into from
Jan 9, 2020

Conversation

pawan
Copy link
Member

@pawan pawan commented Dec 14, 2019

Description (*)

Corrected spelling and adjust white space to increase readability

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 are green)

@pawan pawan requested a review from akaplya as a code owner December 14, 2019 17:32
@m2-assistant
Copy link

m2-assistant bot commented Dec 14, 2019

Hi @pawankparmar. 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 give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Guide documentation.

Copy link
Contributor

@lbajsarowicz lbajsarowicz left a comment

Choose a reason for hiding this comment

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

Please fix Static tests, then PR will be automatically approved.

@magento-engcom-team
Copy link
Contributor

Hi @lbajsarowicz, thank you for the review.
ENGCOM-6474 has been created to process this Pull Request
✳️ @lbajsarowicz, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@magento-engcom-team
Copy link
Contributor

@pawankparmar thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

@pawan
Copy link
Member Author

pawan commented Dec 15, 2019

Please fix Static tests, then PR will be automatically approved.

Hello @lbajsarowicz , do I need to phpcs OR phpcbf file ?

@lbajsarowicz
Copy link
Contributor

Fix your code to pass static tests

@lbajsarowicz
Copy link
Contributor

Maybe I was unclear about the expectations.
What you actually have to do is fix these:
image

*/
public function setExtensionAttributes(
\Magento\Catalog\Api\Data\ProductRender\FormattedPriceInfoExtensionInterface $extensionAttributes
);
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

There has to be an empty line at the end of file.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

* @return $this
* @since 101.1.0
* @since 101.1.0
*/
public function setExtensionAttributes(
\Magento\Catalog\Api\Data\ProductRender\FormattedPriceInfoExtensionInterface $extensionAttributes
Copy link
Contributor

Choose a reason for hiding this comment

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

Import the class, make it single line.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

* @return $this
* @since 101.1.0
* @since 101.1.0
Copy link
Contributor

Choose a reason for hiding this comment

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

There should be only one space.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

*/
public function getExtensionAttributes();

/**
* Set an extension attributes object.
*
* @param \Magento\Catalog\Api\Data\ProductRender\FormattedPriceInfoExtensionInterface $extensionAttributes
* @param \Magento\Catalog\Api\Data\ProductRender\FormattedPriceInfoExtensionInterface $extensionAttributes
Copy link
Contributor

Choose a reason for hiding this comment

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

There should be only one space.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

*/
public function setRegularPrice($regularPrice);

/**
* Retrieve existing extension attributes object or create a new one.
*
* @return \Magento\Catalog\Api\Data\ProductRender\FormattedPriceInfoExtensionInterface|null
* @since 101.1.0
* @since 101.1.0
Copy link
Contributor

Choose a reason for hiding this comment

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

There should be only one space.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

*/
public function getMaxPrice();

/**
* Set the max price of the product
*
* @param string $maxPrice
* @param string $maxPrice
Copy link
Contributor

Choose a reason for hiding this comment

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

There should be only one space.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

@@ -42,16 +42,16 @@ public function setFinalPrice($finalPrice);
* E.g. for product with custom options is price with the most expensive custom option
*
* @return string
* @since 101.1.0
* @since 101.1.0
Copy link
Contributor

Choose a reason for hiding this comment

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

There should be only one space.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

* @return void
* @since 101.1.0
* @since 101.1.0
Copy link
Contributor

Choose a reason for hiding this comment

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

There should be only one space.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

*/
public function getFinalPrice();

/**
* Set the final price: usually it calculated as minimal price of the product
* Can be different depends on type of product
*
* @param string $finalPrice
* @param string $finalPrice
Copy link
Contributor

Choose a reason for hiding this comment

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

There should be only one space.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

@pawan pawan requested a review from lbajsarowicz December 18, 2019 05:35
@pawan
Copy link
Member Author

pawan commented Dec 18, 2019

Maybe I was unclear about the expectations.
What you actually have to do is fix these:
image

Hello @lbajsarowicz , thank you pointing this.

I have fixed other space issue and new line at the end of file.
Still I couldn't fix "There must be exactly one blank line between lines" issue.

In this pull, I just correct spelling and put space between two words!
I am not getting why static test is failing

I have tried following test for my file:
phpcs --standard=PHPCS /home/comp1/Desktop/FormattedPriceInfoInterface.php
phpcs --standard=Squiz /home/comp1/Desktop/FormattedPriceInfoInterface.php
phpcs --standard=PEAR /home/comp1/Desktop/FormattedPriceInfoInterface.php
phpcs --standard=Zend /home/comp1/Desktop/FormattedPriceInfoInterface.php
phpcs --standard=MySource /home/comp1/Desktop/FormattedPriceInfoInterface.php
phpcs --standard=PSR2 /home/comp1/Desktop/FormattedPriceInfoInterface.php
phpcs --standard=PSR1 /home/comp1/Desktop/FormattedPriceInfoInterface.php

None of the above reported "There must be exactly one blank line between lines" issue

Thank you.

@pawan
Copy link
Member Author

pawan commented Dec 24, 2019

@lbajsarowicz

Please fix Static tests, then PR will be automatically approved.

I have fixed Static tests...

@pawan
Copy link
Member Author

pawan commented Jan 1, 2020

@akaplya @lbajsarowicz any updates on PR ? do i need to anything else ?

@pawan
Copy link
Member Author

pawan commented Jan 4, 2020

@magento-engcom-team, any updates on PR ? anything remaining from my side ?

Copy link
Contributor

@lbajsarowicz lbajsarowicz left a comment

Choose a reason for hiding this comment

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

OK

@ghost ghost removed the Progress: needs update label Jan 8, 2020
@magento-engcom-team
Copy link
Contributor

Hi @lbajsarowicz, thank you for the review.
ENGCOM-6474 has been created to process this Pull Request
✳️ @lbajsarowicz, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@engcom-Alfa engcom-Alfa added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Jan 8, 2020
@engcom-Alfa
Copy link
Contributor

QA not applicable

@m2-assistant
Copy link

m2-assistant bot commented Jan 9, 2020

Hi @pawankparmar, 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.

@pawan pawan deleted the spell-fix branch February 15, 2020 12:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants