Remove contender from playground #303
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, Playground exposes flags to run Contender, essentially wrapping Contender's configuration options. The problem is that Contender's scope can be very vast. Forcing Playground to expose and maintain all these flags creates a tight coupling where Playground needs to understand Contender's entire API surface.
The new proposed approach would be to flip the integration direction - have Contender integrate with Playground instead.
Contender would have something like --playground ./folder, which would read the folder's metadata (specifically RPC endpoints) to understand the execution context that Playground has set up.