-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[NIFI-13318] processor stop and configure UX #9548
base: main
Are you sure you want to change the base?
Conversation
reviewing... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few things I noticed while using it...
After transitioning from running -> stopped or stopped -> running, the dialog isn't fully in edit/readonly mode respectively.
- Meaning, if I start a processor that was stopped when I opened the dialog, the button makes the appropriate transition to "Close" and the form won't submit. But the the property editors appear editable and the inputs on the relationships tab remain enabled.
- Inversely, stopping processor that was running when opening the dialog, the dialog becomes "Apply"able but the property editors remain in a read-only state as well as the inputs on the relationships tab.
...p/pages/flow-designer/ui/canvas/items/processor/edit-processor/edit-processor.component.html
Outdated
Show resolved
Hide resolved
...p/pages/flow-designer/ui/canvas/items/processor/edit-processor/edit-processor.component.html
Outdated
Show resolved
Hide resolved
...app/pages/flow-designer/ui/canvas/items/processor/edit-processor/edit-processor.component.ts
Outdated
Show resolved
Hide resolved
…n, update edit processor entity and readonly updates
@rfellows please check these again as they should be working now. |
And for processors with invalid run status: