feat: integrate matchstick into the graph CLI#1549
feat: integrate matchstick into the graph CLI#1549YassinEldeeb wants to merge 122 commits intomainfrom
Conversation
🦋 Changeset detectedLatest commit: cf29a94 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Hey, you'll also need to integrate matchstick-as as well, which is a helper library similar to |
Deploying graph-tooling with
|
| Latest commit: |
cf29a94
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://da203ca1.graph-tooling.pages.dev |
| Branch Preview URL: | https://add-matchstick.graph-tooling.pages.dev |
YassinEldeeb
force-pushed
the
add-matchstick
branch
from
fb76495 to
8c543eb
Compare
| } = await this.parse(TestCommand); | ||
|
|
||
| // Ensure PostgreSQL 14 is installed | ||
| try { |
.changeset/slow-pears-agree.md
Outdated
There was a problem hiding this comment.
let's update this to real message
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| NPM_TOKEN: ${{ secrets.NPM_TOKEN }} | ||
|
|
||
| # CLI |
There was a problem hiding this comment.
uncomment now so we can prep to merge?
packages/cli/package.json
Outdated
| }, | ||
| "dependencies": { | ||
| "@float-capital/float-subgraph-uncrashable": "^0.0.0-alpha.4", | ||
| "@graphprotocol/graph-tooling-napi-utils": "workspace:*", |
There was a problem hiding this comment.
the issue we are facing now is even for test suite we have to build otherwise it will fail 🤔
There was a problem hiding this comment.
yeah, but we build it in the CI, maybe locally we should pre-build before testing too
packages/napi-utils/Cargo.toml
Outdated
| @@ -0,0 +1,43 @@ | |||
| [package] | |||
| name = "matchstick" | |||
| # - host: windows-latest | ||
| # target: i686-pc-windows-msvc | ||
| # build: | | ||
| # rustup target add i686-pc-windows-msvc | ||
| # pnpm build --target i686-pc-windows-msvc |
Co-authored-by: Saihajpreet Singh <saihajpreet.singh@gmail.com>
|
@YassinEldeeb @saihaj is this still planned? |
@alex-pakalniskis @YaroShkvorets can speak to priority for this one |
4 participants
No description provided.