MantisClone comments

Results 132 comments of


                                            MantisClone

fix(readme): test instructions

Superseded by #1493

Add access-control mechanism so payee or payer can delegate request creation and updates (accept, cancel, increase, decrease, addStakeholder)

Hey @ptdatta. Your proposed implementation sounds like it could work. Sure, you're free to work on it. I think the risk of conflicts is low but I'll let you know...

WIP: (for discussion) add topics to accept

Some questions: - What use case does this feature serve? - This idea was motivated by a hacker at ETHRome who wanted to retrieve and filter requests by an arbitrary...

WIP: (for discussion) add topics to accept

@vrolland Sorry this fell through the cracks. I just added it to the [Request Network Tech Backlog](https://github.com/orgs/RequestNetwork/projects/3) and we'll be able to assign priority to this task at our next...

WIP: (for discussion) add topics to accept

Closing in favor of issue: * https://github.com/RequestNetwork/requestNetwork/issues/1548

feat: Create new data access to allow for in-memory transactions.

@alexandre-abrioux your comment convinced me we should inject this feature at the DataAccess layer, instead of the TransactionManager layer. # My Goal 1. RN SDK provides a function to Create...

As a Builder, I want a Subgraph Reference, so I can understand how to use RN's Subgraphs.

These docs should include the deployments on the Arbitrum-based decentralized network. https://github.com/RequestNetwork/payments-subgraph/pull/76

feat!: output ES modules instead of CommonJS

TODO: Consider making `currency` and `utils` packages output ES modules AND CommonJS modules. This would decrease the code churn in the `smart-contracts` package. `smart-contracts` could consume the CommonJS variants of...

Error happened while deserializing the module (stop using parity_wasm)

I searched for ways to disable the `sign-ext` opcodes on the compiler and ran across this issue that seems to indicate that the option to disable `sign-ext` exists :+1: but...

As a Builder, I want package tree-shaking, so I can minimize my build size, compile time, test time, and page load time.

@skiv71 discovered that when we configure `"module": "es2015"` we can still use our packages in a node js application with `require()`. So maybe we don't need to use `"module": "node16"`.