Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add support for threads #46

Merged
merged 6 commits into from
Jan 6, 2025
Merged

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented Dec 22, 2024

Fixes: #37

(tested with TestOrgPleaseIgnore@98427a5)

@aduh95 aduh95 requested a review from a team as a code owner December 22, 2024 22:09
@github-actions github-actions bot added documentation Improvements or additions to documentation automation Changes to the automation labels Dec 22, 2024
automation.md Outdated Show resolved Hide resolved
@AugustinMauroy
Copy link
Member

You use term "tweet" on your changes but we should use "post" it's the word use everywhere

@@ -20,15 +21,25 @@ if (Object.hasOwn(request, 'richTextFile')) {
richTextFile = path.resolve(path.dirname(requestFilePath), request.richTextFile);
request.richText = fs.readFileSync(richTextFile, 'utf-8');
}
const threadElements = request.action !== 'repost' && request.richText?.split(/\n+ {0,3}([-_*])[ \t]*(?:\1[ \t]*){2,}\n+/g);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel that at some point, it would be good to include a proper markdown parser - for example, we can support alternative link text, which is not currently supported in bluesky UI, but supported in their API (the hacker news bot uses this extensively https://bsky.app/profile/newsycombinator.bsky.social), and we can support that too with markdown link syntax, which is a nice-to-have.

replyURL: REPLY_IN_THREAD,
}),
richText,
})) : [request];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel this would be a lot more readable if it's just if-else blocks instead of lots of ternary branches, it kills way more brain cells than it deserves to understand this expression...

@joyeecheung joyeecheung merged commit 5ff8795 into nodejs:main Jan 6, 2025
1 check passed
@aduh95 aduh95 deleted the thread-support branch January 6, 2025 17:44
@joyeecheung joyeecheung mentioned this pull request Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation Changes to the automation documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feature: write a thread in same JSON file
3 participants