posit-dev / posit-dev/py-shiny
[Feature]: add `disabled` argument to `ui.input_text()` (and potentially other inputs)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 135
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 21
Description
Category
Input/Output
Scope
Minor Enhancement
Problem
It'd be great if we could dynamically disable / enable ui.input_text() form fields (similar to the behavior of ui.input_action_button()).
Quite often certain inputs only make sense when another input (e.g. a checkbox) is present and disabling / greying out these fields is a elegant way to handle that (but currently that's not possible).
Solution
It'd be great if a disabled argument could be added to ui.input_text() (and potentially other input types) analogously to ui.input_action_button().
Alternatives (Optional)
No response
Example (Optional)
Impact (Optional)
No response
Contribution? (Optional)
Yes, I can implement (or help).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the existing ui.input_text() and ui.input_action_button() entry points, focusing on how the button's disabled argument behaves. Determine whether the same option should cover only ui.input_text() or other input types, and consider the work done when the selected inputs can be dynamically disabled and enabled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100