This repository was archived by the owner on May 20, 2025. It is now read-only.
Refactor evm_body, evm_responses and evm_examples #262
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
bmoyroud
changed the title
SahilAujla
approved these changes
Oct 19, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem
A lot of our code has been refactored into evm_body.yaml, evm_responses.yaml, evm_examples.yaml.
More often than not, this is not needed as the components are only used in 1 spec.
Splitting specs across multiple files makes it harder to understand what the spec is doing quickly.
Solution
Keep only code shared across multiple specs in evm_body.yaml, evm_responses.yaml, evm_examples.yaml.