this post was submitted on 10 Dec 2022
1 points (100.0% liked)

Lemmy

12524 readers
9 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago
MODERATORS
 

I've written Go bindings for Lemmy's HTTP API. If anyone wants to use them, the import path is go.arsenm.dev/go-lemmy. The repo is at https://gitea.arsenm.dev/Arsen6331/go-lemmy with a mirror on GitHub: https://github.com/Arsen6331/go-lemmy.

you are viewing a single comment's thread
view the rest of the comments
[–] picoblaanket@lemmy.ml 1 points 2 years ago (1 children)

Hey, thank you for the reply.

I went through the js-client docs, and the available methods.

Seems GetPost is the one required for importing comments.

I suppose it would arrive (to Hugo) as a json object (identical to the one in the console log of a Lemmy post).

Within that GetPost data, I see that each nested-comment has a parent-comment-id.

**

1 - So would the idea be to rebuild a UI for the nested comments section?

(and then connect other JS-client objects to new UI-elements, such as voting-buttons and reply-inputs)?

2 - Or is there an easier way to display the data, since [Lemmy] and [all built-Hugo-pages] are running on the same server/domain?

(and since Lemmy already has the UI code to build nested comments)

[NOTE: Lemmy is in docker, Hugo-pages are in /srv/]

**

Essentially - What is the suggested/optimal way to display that js-client info on a js-capable static page?

[Please forgive any naiveté in those questions. I am willing to experiment with new approaches.]

I appreciate your response. It's good to know that this technique is available.

[–] Arsen6331@lemmygrad.ml 1 points 2 years ago

If you want to actually display this information, you will need to use your own UI elements. If you want, you can simply reuse the code for lemmy-ui and modify it for whatever you need.