-
Notifications
You must be signed in to change notification settings - Fork 9
feat: contracts and project providers + cleanup #597
Conversation
be0048a
to
32001ca
Compare
e1b0836
to
65b6040
Compare
9eb6eb7
to
9b7d3d8
Compare
ce5c0bd
to
fb16197
Compare
Perhaps, for instant finality, the The following is a work around for local debugging
|
@kratico thank you for the extraordinary contracts fix! The contracts example now executes in less than a second! |
@@ -23,7 +23,7 @@ export function handler(env: Env): Handler { | |||
return await provider.handle(request, pathInfo) | |||
} catch (e) { | |||
if (e instanceof Response) return e | |||
if (env.dbg) console.error(e) | |||
console.error(e) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can re-add the toggling on/off when we tackle a comprehensive approach to logging from the Capi server (perhaps using Logger
from deno_std
). I plan to take a pass at this in a PR that also addresses #649.
Just for reference, this would probably also fix this implicitly: paritytech/substrate-contracts-node#160 |
c368321
to
7df315d
Compare
Resolves #626
This PR introduces two new providers:
ProjectProvider
, which allows easy use within a substrate project. Simplycapi -- deno run -A my_script.ts
in your Substrate project.my_script.ts
substrate-contracts-node
(per the request of @wottpal).This PR also...
FrameBinProvider
classEnv
Next up: #649