microsoft / microsoft/DurableFunctionsMonitor
Feature request: Action buttons should be disabled if runtimeStatus doesn't allow that action
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 290
- Forks
- 46
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Version: DurableFunctionsMonitor.DotNetIsolated, 6.5.0-beta2
These buttons in the UI are clickable regardless of runtimeStatus for the orchestration instance. If you then click them, an (non-intuitive) Exception is thrown.
Alternatively, fix the error messages to be more intuitive. In above example, maybe: "Failed to suspend. Not allowed for status 'Failed'."
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 locating the UI components for orchestration action buttons and the code that reads an instance's runtimeStatus. Review which actions are invalid for each status, then verify that invalid buttons are disabled or that the resulting errors clearly identify the disallowed action and status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- devtools, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100