Skip to content

chore: put legacy collections under feature flag#923

Merged
austinabell merged 5 commits into
masterfrom
austin/legacy_feat
Oct 19, 2022
Merged

chore: put legacy collections under feature flag#923
austinabell merged 5 commits into
masterfrom
austin/legacy_feat

Conversation

@austinabell
Copy link
Copy Markdown
Contributor

closes #869

This doesn't functionally change anything because it's enabled by default, but allows devs to remove this section, and this will be deprecated in the next major version

Copy link
Copy Markdown
Contributor

@ChaoticTempest ChaoticTempest left a comment

Choose a reason for hiding this comment

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

hmm, that one test failure for simulate_simple_approve seems weird, but maybe bringing up at least 16 sandbox nodes at the same time could make it very slow. Did you ever try upping the timeout seconds?

Comment thread .github/workflows/test.yml Outdated
- run: rustup target add wasm32-unknown-unknown
- name: Test
run: cargo test --all --features unstable
run: cargo test --all --features unstable --features legacy
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

optional: it's kinda weird that --features can be supplied multiple times like this. Normally I just put --features unstable,legacy, but up to you

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.

Put old collections under legacy feature

2 participants