Current Behavior

comments.create accepts the following parameters:

signerAddress: string, 
token: string, 
comment: string, 
threadId: string, 
url: string, 
metadata?: Dictionary<any>

Expected Behavior

Should accept a replyTo: string parameter with a valid comment _id value to set that comment as a reply.

Environment

• Version: "^0.3.17"
• Platform: MacOS
• Node.js Version: "v14.17.3"

Current Behavior

I signed, verified and generated jwt, I can create comments normally, but I can't update and delete comments, and they report similar errors (A user can only edit/delete their own comment)

Expected Behavior

I compared the commentId, signerAddress, token in the network request, I don't seem to pass it wrong, it should be successful, maybe I'm missing something? o(╥﹏╥)o

Steps to Reproduce the Problem

Environment

• "@theconvospace/sdk": "^0.4.15",
• Platform: Win
• Node.js Version: v16.13.1

data is an array of array so you need to access the first item of data to actually get the size of the comment list. Something like:

display={data && data[data.length - 1]?.length > size ? 'flex' : 'none'}

Hey team,

We've noticed that you're referencing a subgraph deployed on The Graph's hosted service in this repository. Just a heads-up: after June 12th, hosted service subgraph endpoints will no longer be available as the offering is being deprecated.

If you are the subgraph owner or maintainer, it's time to upgrade your subgraph to the network. This ensures everything keeps running smoothly and you get access to all the latest features and improvements. Here is a quick guide with all the upgrade steps.

If you're not the subgraph owner or maintainer, check Graph Explorer to see if the subgraph development team has already upgraded to the network. If you don’t find an upgraded subgraph, a friendly nudge to the subgraph development team would be greatly appreciated—it's a quick process that benefits everyone. Here's the upgrade guide with all the necessary steps for the subgraph development team.

Once the subgraph is upgraded to the network, you can create an API key and updated query URL in Subgraph Studio then update this repository to query from the new endpoint, https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>

Need more support or have more questions? Feel free to reach out to [email protected]. We're here to help!

Cheers,

Paka

Current Behavior

Using the SDK i can get a jwt and validate it successfully but when i use
convo.threads.create( "address", "jwt", "My new thread", "Placeholder description", "an url", true, false, ["address"], ["address"], ["habitat", "dao"] )
I get the response error:
{"success":false,"error":"Error: unsupported JSON value type"}

Expected Behavior

It should create a new thread

Environment

• Version: "@theconvospace/sdk": "0.1.16"
• Platform: Mozilla firefox, linux
• Node.js Version: v14.17.6

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀