Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
discourse-js
Advanced tools
$ npm i discourse-js
import Discourse from "discourse-js";
const apiKey = "<api-key-from-discourse>";
const baseUrl = "<your-discourse-url>" || "http://localhost:3000";
const discourse = new Discourse(apiKey, baseUrl);
discourse.posts
.create({
api_username: "karl",
topic_id: 11, // optional (required for creating a new post on a topic.)
raw: "Hello World",
imageUri: imageUri // optional to create a post/topic with an image.
})
.then(res => console.log(res))
.catch(err => console.log(err));
Todo
discourse.groups
.getMembers({ group_name: "group-name" })
.then(res => console.log(res))
.catch(err => console.log(err));
Todo
Todo
discourse.posts
.create({
api_username: "karl",
topic_id: 11, // optional (required for creating a new post on a topic.)
raw: "Hello World",
imageUri: imageUri // optional to create a post/topic with an image.
})
.then(res => console.log(res))
.catch(err => console.log(err));
discourse.posts
.like({ id: 72 })
.then(res => console.log(res))
.catch(err => console.log(err));
discourse.posts
.unlike({ id: 72 })
.then(res => console.log(res))
.catch(err => console.log(err));
Note: You can only unlike
a post within 5 - 10 minutes after you have liked
it. Think of unlike
more so like an undo.
See this post here and here for information around the undocumented time limit on unliking a liked post.
discourse.posts
.reply({
topic_id: 72,
raw: 'Hello World',
reply_to_post_number: 14
})
.then(res => console.log(res))
.catch(err => console.log(err));
discourse.topics
.getTopic({ id })
.then(res => console.log(response)}
.catch(err => console.log(err))
Topics have a chunk size of 20, which mean you will only get 20 posts back in one get. This can cause weird problems with nested replies and long threads. You can override this by passing print: true
. Note this sets the chunk size to 1000. See API: Getting all posts in a topic
discourse.topics
.getTopic({
id,
print: true
})
.then(res => console.log(response)}
.catch(err => console.log(err))
discourse.users
.getUser({ username })
.then(res => console.log(response)}
.catch(err => console.log(err))
This is if you are developing the discourse-js
API locally on your machine.
# Clone the repo
$ git clone git@gitlab.com:theworkshop/discourse-js.git
$ cd discourse-js
$ pwd|pbcopy # Copies the current working directory /path/to/discourse-js/
# cd into the directory you want to test locally.
$ npm install /path/to/discourse-js/
Why not just use npm link
?:
For speed and productivity. Symlinks do not work with React Native 💩📲.
Read more about npm link and why we do this here.
You will also need a Discourse server running. This can be local or running in the cloud.
MIT
FAQs
A client-side javascript wrapper for the discourse API.
The npm package discourse-js receives a total of 1 weekly downloads. As such, discourse-js popularity was classified as not popular.
We found that discourse-js demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.