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

Add common-testnets package #489

Merged
merged 13 commits into from
Dec 13, 2024
Merged

Add common-testnets package #489

merged 13 commits into from
Dec 13, 2024

Conversation

yivlad
Copy link
Contributor

@yivlad yivlad commented Dec 12, 2024

No description provided.

Copy link

vercel bot commented Dec 12, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
app-storybook ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 13, 2024 9:45am
spark-app-production ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 13, 2024 9:45am
spark-app-staging ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 13, 2024 9:45am

Copy link

github-actions bot commented Dec 12, 2024

📦 Size Report

Path Size Diff
JS 1.3 MB 934 B (+0.07% 🔺)
CSS 23.28 KB 0 B (0%)

@yivlad yivlad force-pushed the yivlad/add-common-testnets-package branch from ad0bebf to a57ae32 Compare December 12, 2024 13:35

assert(result === true, 'revert failed')

// anvil snapshot are "burned" after revert so we need to create a new one
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
// anvil snapshot are "burned" after revert so we need to create a new one
// anvil snapshots are "burned" after revert so we need to create a new one

@@ -65,7 +65,8 @@ jobs:
- run: pnpm install

- run: pnpm check
- run: pnpm verify # does linting, type checking, and tests in parallel
- name: Verify # verifies all packages except common-testnets
run: pnpm run --parallel --aggregate-output --reporter append-only --filter './packages/{app,common-nodejs,common-universal}' verify
Copy link
Contributor

Choose a reason for hiding this comment

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

i think we can simplify this. So the mental model should be that verify is fast (linting, unit tests etc) and we can always run in on every single project. In case of common-testnets verify would run eslint and typecheck but no tests because these are not unit tests but rather integration/e2e tests. So the task should be renamed to test-e2e and then the CI job for testnets runs only that.

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.

3 participants