mirror of
https://github.com/anomalyco/opentui.git
synced 2026-04-25 04:55:58 +03:00
[GH-ISSUE #219] Feedback + contributing guideline #826
Labels
No labels
bug
core
documentation
feature
good first issue
help wanted
pull-request
question
react
solid
tmux
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/opentui#826
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hanpham32 on GitHub (Oct 20, 2025).
Original GitHub issue: https://github.com/anomalyco/opentui/issues/219
Since learning about OpenTUI from Opencode, I'm beginning to use OpenTUI to build new TUI apps. It's been a fun experience using TS to put together a UI in the terminal. I can see OpenTUI be a powerful framework for future TUI app developments. I would love to contribute to this open source project, however, there isn't a standard guideline for that. Would also love to see an official OpenTUI API documentation. I understand this is an on-going development framework so there will be many breaking changes.
@kommander commented on GitHub (Oct 20, 2025):
Cool, want to write a guideline? :) Bug fixes are always welcome, feature suggestions, also in the form of a PR as well. Features are subject to discussion though and I cannot guarantee anything. Support/binding packages like react/solid/vue are handled by their respective maintainers, where I am also trying to look after solid, as that is what is used in opencode. Should add tests and must pass in the pipeline. Otherwise I am open to suggestions on what the guidelines could be.
@hanpham32 commented on GitHub (Oct 21, 2025):
Yes, happy to work on this :)