Skip to content
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.

Declare strict types #45

Merged
merged 1 commit into from
Nov 23, 2018

Conversation

tux-rampage
Copy link
Contributor

@tux-rampage tux-rampage commented Nov 16, 2018

All source files should declare strict types.

See Issue #41

  • Are you fixing a bug?

    • Detail how the bug is invoked currently.
    • Detail the original, incorrect behavior.
    • Detail the new, expected behavior.
    • Base your feature on the master branch, and submit against that branch.
    • Add a regression test that demonstrates the bug, and proves the fix.
    • Add a CHANGELOG.md entry for the fix.
  • Are you creating a new feature?

    • Why is the new feature needed? What purpose does it serve?
    • How will users use the new feature?
    • Base your feature on the develop branch, and submit against that branch.
    • Add only one feature per pull request; split multiple features over multiple pull requests
    • Add tests for the new feature.
    • Add documentation for the new feature.
    • Add a CHANGELOG.md entry for the new feature.
  • Is this related to quality assurance?
    This assures the common best practices of ZF components

  • Is this related to documentation?

@tux-rampage tux-rampage added this to the 3.2.0 milestone Nov 16, 2018
@tux-rampage tux-rampage added this to In progress in QA via automation Nov 16, 2018
@tux-rampage tux-rampage requested review from a team and Ocramius November 16, 2018 20:24
@Ocramius
Copy link
Member

Ocramius commented Nov 16, 2018 via email

@tux-rampage
Copy link
Contributor Author

Definitly a goal. Should I add it in this PR or another one?

@Ocramius
Copy link
Member

Ocramius commented Nov 17, 2018 via email

@tux-rampage tux-rampage mentioned this pull request Nov 20, 2018
17 tasks
@Ocramius
Copy link
Member

Now this can be rebased 👌

Can you try and check which level of PHPStan works in the test suite?

@tux-rampage
Copy link
Contributor Author

Sure will look at it later, maybe tomorrow. Thanks.

@tux-rampage tux-rampage changed the base branch from master to develop November 22, 2018 08:18
@@ -225,7 +227,7 @@ public function setTypePreference(string $type, string $preference, ?string $con
public function setAlias(string $name, string $class) : self
{
if (! class_exists($class) && ! interface_exists($class)) {
throw new Exception\ClassNotFoundException('Could not find class "' . $class . '"');
throw new Exception\ClassNotFoundException($class);
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is a nitpick spotted while working on this. This call duplicates the message because ClassNotFoundException only expects the class name.

@tux-rampage
Copy link
Contributor Author

@Ocramius rebase is complete. I also changed the target branch from master to develop (idk why I didn't do that when opening this PR).

@Ocramius Ocramius self-assigned this Nov 23, 2018
Copy link
Member

@Ocramius Ocramius left a comment

Choose a reason for hiding this comment

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

🚢

QA automation moved this from In progress to Reviewer approved Nov 23, 2018
@Ocramius Ocramius merged commit 34fe8bf into zendframework:develop Nov 23, 2018
QA automation moved this from Reviewer approved to Done Nov 23, 2018
@tux-rampage tux-rampage deleted the feature/strict-types branch November 27, 2018 09:47
@tux-rampage tux-rampage mentioned this pull request Nov 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
QA
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

2 participants