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

Add option to use syncronous processor #16

Closed
4 tasks done
The1029 opened this issue Jan 5, 2024 · 1 comment
Closed
4 tasks done

Add option to use syncronous processor #16

The1029 opened this issue Jan 5, 2024 · 1 comment
Labels
🤷 no/invalid This cannot be acted upon 👎 phase/no Post cannot or will not be acted on

Comments

@The1029
Copy link

The1029 commented Jan 5, 2024

Initial checklist

Problem

remark-retext currently returns an async processor with no option to change this.

Solution

By adding an option to request a syncronous processor instead, the plugin would become more versatile.

Alternatives

Do not use remark-retext in syncronous functions.

@github-actions github-actions bot added 👋 phase/new Post is being triaged automatically 🤞 phase/open Post is being triaged manually and removed 👋 phase/new Post is being triaged automatically labels Jan 5, 2024
@JounQin
Copy link
Member

JounQin commented Jan 5, 2024

You didn't provide any valuable input, why it's needed, why the async version does not work for you.

@JounQin JounQin added the 🤷 no/invalid This cannot be acted upon label Jan 5, 2024
@github-actions github-actions bot added 👎 phase/no Post cannot or will not be acted on and removed 🤞 phase/open Post is being triaged manually labels Jan 5, 2024
@github-actions github-actions bot closed this as completed Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤷 no/invalid This cannot be acted upon 👎 phase/no Post cannot or will not be acted on
Development

No branches or pull requests

2 participants