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

[DEMO] V5.0.21 rebased #2136

Closed
wants to merge 6 commits into from
Closed

Conversation

stenolog
Copy link
Contributor

@stenolog stenolog commented Mar 9, 2024

re #2137

Demonstration of how simple it is to create PRs with a clean history.

This would replace:

ccellado and others added 5 commits March 9, 2024 14:12
Add changes to ergo-core readme
extract PoPowAlgosSpec -> PoPowAlgosWithDBSpec

extract SerializationTest -> SerializationCoreTest

extract JsonSerializationSpec -> JsonSerializationCoreSpec

move scorex.testkit.SerializationTests -> ergo-core/org.ergoplatform/utils

NiPoPoWVerifierSpec has to stay in node's test since ChainGenerators it requires uses ErgoHistory

Create ChainSettingsReader in ergocore

Refactor generators to use Object instead of trait. To avoid OOP inheritance spagetti

Remove scores.testkit.CoreGenerators

Move scorex.testkit.generators.ObjectGenerators -> ergo-core/org.ergoplatform.utils.generators.CoreGenerators

Extract ergo-node specific ConnectedPeerGenerators from CoreGenerators

Move DefaultFakePowScheme to ergo-core

Dissect ErgoTestConstants into ErgoCoreTestConstants & ErgoNodeTestConstants

Move settings.LaunchParameters to ergo-core

Dissect ErgoTransactionGenerators into ErgoCoreTransactionGenerators & ErgoNodeTransactionGenerators

Dissect part of VotingSpecification to ErgoNodeVotingSpecification
fix test 'valid application of correct extension'

fix test 'validation of field value sizes'

provide alternate test-generators
Add ergo-core testing and publishing snapshot on PR branch push

Fix ergo-core multiversion tests
@stenolog stenolog mentioned this pull request Mar 10, 2024
Closed
Copy link
Member

@kushti kushti left a comment

Choose a reason for hiding this comment

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

I do not understand why you did it for this repo only, and not for 5.0.14 upcoming release in sigma. Makes sense to start with upstream dependencies

@kushti kushti closed this Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants