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

Simplify usage by supporting new default loop #182

Merged
merged 2 commits into from
Jul 11, 2021

Conversation

clue
Copy link
Member

@clue clue commented Jul 8, 2021

This changeset simplifies usage by supporting the new default loop.

// old (still supported)
$factory = new React\Dns\Resolver\Factory();
$resolver = $factory->create($config, $loop);

// new (using default loop)
$factory = new React\Dns\Resolver\Factory();
$resolver = $factory->create($config);

Builds on top of reactphp/event-loop#226, reactphp/event-loop#229 and reactphp/event-loop#232
Refs reactphp/stream#159

@clue clue added this to the v1.8.0 milestone Jul 8, 2021
@clue
Copy link
Member Author

clue commented Jul 8, 2021

The first commit updates this to the currently unreleased EventLoop component to show how the new default loop can be used in this component (the build should be green). The second commit updates this to the release that has yet to be tagged. This is expected to fail at the moment and should be green once the release is tagged and the build is restarted.

This is ready for review. I will restart the build and merge once reviewed and the EventLoop component is tagged.

@clue clue changed the title [WIP] Simplify usage by supporting new default loop Simplify usage by supporting new default loop Jul 11, 2021
@clue
Copy link
Member Author

clue commented Jul 11, 2021

Restarted build and everyhing's green now that reactphp/event-loop v1.2.0 has been released :shipit:

@clue clue merged commit 46feda0 into reactphp:master Jul 11, 2021
@clue clue deleted the default-loop branch July 11, 2021 12:37
WyriHaximus added a commit to WyriHaximus-labs/dns that referenced this pull request May 22, 2024
This changeset improves PHP 8.4+ support by avoiding implicitly nullable types as discussed in reactphp/promise#260.

I'm planning to add native types to the public API and introduce PHPStan in follow-up PRs.

Once merged, we should apply similar changes to all our upcoming v3 components. On top of this, we should backport similar changes to the v1 branch.

Builds on top of reactphp#182, reactphp#222 and reactphp/promise#260
WyriHaximus added a commit to WyriHaximus-labs/dns that referenced this pull request May 30, 2024
This changeset improves PHP 8.4+ support by avoiding implicitly nullable types as discussed in reactphp/promise#260.

I'm planning to add native types to the public API and introduce PHPStan in follow-up PRs.

Once merged, we should apply similar changes to all our upcoming v3 components. On top of this, we should backport similar changes to the v1 branch.

Builds on top of reactphp#182, reactphp#222 and reactphp/promise#260
WyriHaximus added a commit to WyriHaximus-labs/dns that referenced this pull request Jun 5, 2024
This changeset improves PHP 8.4+ support by avoiding implicitly nullable types as discussed in reactphp/promise#260.

I'm planning to add native types to the public API and introduce PHPStan in follow-up PRs.

Once merged, we should apply similar changes to all our upcoming v3 components. On top of this, we should backport similar changes to the v1 branch.

Builds on top of reactphp#182, reactphp#222 and reactphp/promise#260
WyriHaximus added a commit to WyriHaximus-labs/dns that referenced this pull request Jun 5, 2024
This changeset improves PHP 8.4+ support by avoiding implicitly nullable types as discussed in reactphp/promise#260.

I'm planning to add native types to the public API and introduce PHPStan in follow-up PRs.

Once merged, we should apply similar changes to all our upcoming v3 components. On top of this, we should backport similar changes to the v1 branch.

Builds on top of reactphp#182, reactphp#222 and reactphp/promise#260
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.

2 participants