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

refactor: change config to single struct #1328

Merged
merged 2 commits into from
Aug 23, 2023

Conversation

driftluo
Copy link
Contributor

@driftluo driftluo commented Aug 16, 2023

What this PR does / why we need it:

This PR change metadata config to a single struct, this is a break change

Which docs this PR relation:

Which toolchain this PR adaption:

!!Breaking Change!!

CI Description

CI Name Description
Chaos CI Test the liveness and robustness of Axon under terrible network condition
Cargo Clippy Run cargo clippy --all --all-targets --all-features
Coverage Test Get the unit test coverage report
E2E Test Run end-to-end test to check interfaces
Code Format Run cargo +nightly fmt --all -- --check and cargo sort -gwc
Web3 Compatible Test Test the Web3 compatibility of Axon
v3 Core Test Run the compatibility tests provided by Uniswap V3
OCT 1-5 | 6-10 | 11 | 12-15 | 16-19 Run the compatibility tests provided by OpenZeppelin

CI Usage

Check the CI you want to run below, and then comment /run-ci.

CI Switch

  • Chaos CI
  • Cargo Clippy
  • Coverage Test
  • E2E Tests
  • Code Format
  • Unit Tests
  • Web3 Compatible Tests
  • OCT 1-5 And 12-15
  • OCT 6-10
  • OCT 11
  • OCT 16-19
  • v3 Core Tests

@driftluo driftluo changed the title refactor: change config to single struct refactor(BREAK CHANG): change config to single struct Aug 17, 2023
@driftluo driftluo force-pushed the change-metadata-config-to-single-struct branch from bca4586 to 0f2b30b Compare August 17, 2023 06:04
@driftluo driftluo changed the title refactor(BREAK CHANG): change config to single struct refactor: change config to single struct Aug 17, 2023
@driftluo driftluo force-pushed the change-metadata-config-to-single-struct branch 2 times, most recently from 32b525a to a9c4116 Compare August 17, 2023 08:36
@driftluo driftluo marked this pull request as ready for review August 17, 2023 08:41
@driftluo driftluo requested a review from a team as a code owner August 17, 2023 08:41
@driftluo driftluo requested review from ahonn and Simon-Tl August 17, 2023 08:41
@Flouse Flouse requested review from KaoImin and removed request for ahonn and Simon-Tl August 18, 2023 02:39
@driftluo driftluo force-pushed the change-metadata-config-to-single-struct branch from a9c4116 to 96cb8e2 Compare August 18, 2023 03:18
@Flouse

This comment was marked as outdated.

Flouse

This comment was marked as outdated.

@driftluo driftluo force-pushed the change-metadata-config-to-single-struct branch 3 times, most recently from 6bcc73d to 5cf2425 Compare August 22, 2023 01:59
@driftluo
Copy link
Contributor Author

/run-ci

@driftluo driftluo force-pushed the change-metadata-config-to-single-struct branch from 5cf2425 to 35821a3 Compare August 22, 2023 09:12
@driftluo driftluo force-pushed the change-metadata-config-to-single-struct branch from 35821a3 to 2f57c95 Compare August 23, 2023 06:07
@driftluo driftluo force-pushed the change-metadata-config-to-single-struct branch from 2f57c95 to 1ffe169 Compare August 23, 2023 07:06
@Flouse Flouse self-requested a review August 23, 2023 07:30
@KaoImin
Copy link
Contributor

KaoImin commented Aug 23, 2023

/run-ci

Copy link
Collaborator

@yangby-cryptape yangby-cryptape left a comment

Choose a reason for hiding this comment

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

I didn't understand the implementation details of this feature clearly.

Since there is no obvious issue in coding, let's merge it to avoid blocking the following part; then we can test the feature later.

@driftluo driftluo enabled auto-merge August 23, 2023 09:20
@driftluo driftluo added this pull request to the merge queue Aug 23, 2023
Merged via the queue into main with commit 02a5bf7 Aug 23, 2023
@KaoImin KaoImin deleted the change-metadata-config-to-single-struct branch August 23, 2023 09:24
@driftluo driftluo mentioned this pull request Aug 23, 2023
11 tasks
@yangby-cryptape yangby-cryptape restored the change-metadata-config-to-single-struct branch August 23, 2023 10:14
@yangby-cryptape yangby-cryptape deleted the change-metadata-config-to-single-struct branch August 23, 2023 10:57
github-merge-queue bot pushed a commit that referenced this pull request Aug 23, 2023
<!--  Thanks for sending a pull request! -->

## What this PR does / why we need it?

This PR fixes genesis hash change on #1328 

### What is the impact of this PR?

No Breaking Change

<!--
**Special notes for your reviewer**:
NIL

**PR relation**:
- Ref #

**Which issue(s) this PR fixes**:
You could link a pull request to an issue by using a supported keyword
in the pull request's description or in a commit message.

- Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
see [Linking a pull request to an issue using a
keyword](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)
or [Manually linking a pull request to an issue using the pull request
sidebar](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-or-branch-to-an-issue-using-the-issue-sidebar)

-->

<details><summary>CI Settings</summary><br/>

<!--  Have I run `make ci`? -->
### **CI Usage**

**Tip**: Check the CI you want to run below, and then comment `/run-ci`.

**CI Switch**

- [ ] Cargo Clippy
- [ ] Coverage Test
- [ ] E2E Tests
- [ ] Code Format
- [ ] Unit Tests
- [ ] Web3 Compatible Tests
- [ ] OCT 1-5 And 12-15
- [ ] OCT 6-10
- [ ] OCT 11
- [ ] OCT 16-19
- [ ] v3 Core Tests

### **CI Description**

| CI Name | Description |
| ----------------------------------------- |
-------------------------------------------------------------------------
|
| *Chaos CI* | Test the liveness and robustness of Axon under terrible
network condition |
| *Cargo Clippy* | Run `cargo clippy --all --all-targets --all-features`
|
| *Coverage Test* | Get the unit test coverage report |
| *E2E Test* | Run end-to-end test to check interfaces |
| *Code Format* | Run `cargo +nightly fmt --all -- --check` and `cargo
sort -gwc` |
| *Web3 Compatible Test* | Test the Web3 compatibility of Axon |
| *v3 Core Test* | Run the compatibility tests provided by Uniswap V3 |
| *OCT 1-5 \| 6-10 \| 11 \| 12-15 \| 16-19* | Run the compatibility
tests provided by OpenZeppelin |

<!--
#### Deprecated CIs
- [ ] Chaos CI
-->
</details>
KaoImin pushed a commit that referenced this pull request Aug 25, 2023
<!--  Thanks for sending a pull request! -->

## What this PR does / why we need it?

This PR fixes genesis hash change on #1328 

### What is the impact of this PR?

No Breaking Change

<!--
**Special notes for your reviewer**:
NIL

**PR relation**:
- Ref #

**Which issue(s) this PR fixes**:
You could link a pull request to an issue by using a supported keyword
in the pull request's description or in a commit message.

- Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
see [Linking a pull request to an issue using a
keyword](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)
or [Manually linking a pull request to an issue using the pull request
sidebar](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#manually-linking-a-pull-request-or-branch-to-an-issue-using-the-issue-sidebar)

-->

<details><summary>CI Settings</summary><br/>

<!--  Have I run `make ci`? -->
### **CI Usage**

**Tip**: Check the CI you want to run below, and then comment `/run-ci`.

**CI Switch**

- [ ] Cargo Clippy
- [ ] Coverage Test
- [ ] E2E Tests
- [ ] Code Format
- [ ] Unit Tests
- [ ] Web3 Compatible Tests
- [ ] OCT 1-5 And 12-15
- [ ] OCT 6-10
- [ ] OCT 11
- [ ] OCT 16-19
- [ ] v3 Core Tests

### **CI Description**

| CI Name | Description |
| ----------------------------------------- |
-------------------------------------------------------------------------
|
| *Chaos CI* | Test the liveness and robustness of Axon under terrible
network condition |
| *Cargo Clippy* | Run `cargo clippy --all --all-targets --all-features`
|
| *Coverage Test* | Get the unit test coverage report |
| *E2E Test* | Run end-to-end test to check interfaces |
| *Code Format* | Run `cargo +nightly fmt --all -- --check` and `cargo
sort -gwc` |
| *Web3 Compatible Test* | Test the Web3 compatibility of Axon |
| *v3 Core Test* | Run the compatibility tests provided by Uniswap V3 |
| *OCT 1-5 \| 6-10 \| 11 \| 12-15 \| 16-19* | Run the compatibility
tests provided by OpenZeppelin |

<!--
#### Deprecated CIs
- [ ] Chaos CI
-->
</details>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants