WIP: Bindings #1706
No reviewers
Labels
No labels
DB & Storage
Deployment
Error Handling & Logging
Maintenance
Payment Backend
backport
backport v0.13.x
backport v0.14.x
backport v0.15.x
bindings
blocked
bug
cdk-sql
ci
cli
deps
documentation
duplicate
enhancement
good first issue
help wanted
invalid
keep-open
ldk-node-ui
migrations
mint
mutation-testing
needs rebase
needs review
new nut
nut change
question
ready
rust-version
rustfmt
stacked hold
stale
testing
wallet
weekly-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
cashubtc/cdk!1706
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "crodas/feature/bindings"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Prototype to have a monorepo for all the bindings
Notes to the reviewers
Suggested CHANGELOG Updates
CHANGED
ADDED
REMOVED
FIXED
Checklist
just final-checkbefore committingNice. I think this is generally in the right direction though I didn't try to run anything.
@ -0,0 +13,4 @@integration layers where Rust code can be adapted to the conventions and nativecapabilities of each platform or language runtime.[1]: https://gitlab.com/ark-bitcoin/bark-ffi-bindingsShould make this more what it is and how to use it and when we need to modify it. We can credit bark at the end of the readme.
@ -0,0 +1,31 @@[package]We should pick a tag, looks like payjoin is using v0.1.0+v0.30.0, do we need main. If so whatever commit is working for us.
@ -0,0 +1,126 @@//! Build scriptCan we just add a little more detail on why we need to patch and if it might change in the future as I understand this is required but it could be fragile, so to save us some time debugging in the future. Also if we could track what we need in order to avoid patching to get the upstream that would be great.
@ -0,0 +1,254 @@#!/bin/bashWe need to define this in a nix and not use rustup
Should define this in a flake and not use rustup
@ -28,7 +28,7 @@ serde = { workspace = true, features = ["derive", "rc"] }serde_json = { workspace = true }Can this be a workspace dep, we use it in multiple places?
@ -1908,6 +1908,38 @@ pub enum WalletDbBackend {},We use the enum because of a uniffi limitation of being able to use a trait directly, I'm guessing? Can we just add a comment explaining that?
Should we add some constructors on the enum, new_sqlite(path), new_psgl(url) for example? Think that would be easier for downstream to use.
@ -1908,6 +1908,38 @@ pub enum WalletDbBackend {},Yeah, I'll expand on that. But that is the reason
I notice the flake.lock is not changed after adding the dart overlay. This could be what is causing the rate limiting as this needs to be updated.
nix flake lockshould be run and the new lock file committed.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.