Skip to content

Typo cleanup for app #13283

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 83 commits into from
Jan 22, 2018
Merged

Typo cleanup for app #13283

merged 83 commits into from
Jan 22, 2018

Conversation

akiojalehto
Copy link
Member

@akiojalehto akiojalehto commented Jan 19, 2018

Description

I was adjusting my code inspection and made a little larger cleanup for typos while at it. No breaking changes, just misspellings.

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)

Copy link
Contributor

@ishakhsuvarov ishakhsuvarov left a comment

Choose a reason for hiding this comment

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

Changes look good to me. I am going to invite more people for the review just in case, as change set is rather big.

 - Suppressed warning for unused formal parameter in constructor so that static tests pass
 - Marked unused property as deprecated for future removal
@ishakhsuvarov
Copy link
Contributor

@akiojalehto Thank you for contribution. Changes look good to me.
I had to add a suppress warning in one place as tests detect issues not related to this PR (Static tests are executed only on the files changed).

@akiojalehto
Copy link
Member Author

@ishakhsuvarov Great, thank you. I noticed that the test result was unrelated to PR, but didn't spot the logic for it.

@@ -51,7 +51,7 @@ public function setMaxPrice($maxPrice);

/**
* Set max regular price
* Max regular price is the same, as maximum price, except of excluding calculating special price and catalogules
* Max regular price is the same, as maximum price, except of excluding calculating special price and catalogues
Copy link
Contributor

Choose a reason for hiding this comment

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

catalog rules maybe?

Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like yes

@ishakhsuvarov
Copy link
Contributor

@akiojalehto I took the liberty of updating the doc block with more appropriate wording. Hope you don't mind

@akiojalehto
Copy link
Member Author

@ishakhsuvarov Don't mind at all, it's much faster if you guys update directly all the things you see more appropriate.

@magento-team magento-team merged commit 5c30560 into magento:2.3-develop Jan 22, 2018
magento-team pushed a commit that referenced this pull request Jan 22, 2018
@mzeis mzeis mentioned this pull request May 10, 2018
4 tasks
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.

4 participants