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

[NIFI-13318] processor stop and configure UX #9548

Merged
merged 28 commits into from
Dec 10, 2024

Conversation

scottyaslan
Copy link
Contributor

@scottyaslan scottyaslan commented Nov 21, 2024

Kapture 2024-11-21 at 15 11 46

And for processors with invalid run status:

Screenshot 2024-11-21 at 3 23 29 PM

@scottyaslan scottyaslan added the new ui Pull requests for work relating to the new user interface being developed. label Nov 21, 2024
@rfellows
Copy link
Contributor

reviewing...

Copy link
Contributor

@rfellows rfellows left a 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.

@scottyaslan
Copy link
Contributor Author

I have also added the processor bulletins:

Screenshot 2024-11-25 at 11 33 09 AM Screenshot 2024-11-25 at 11 33 27 AM Screenshot 2024-11-25 at 11 37 45 AM Screenshot 2024-11-25 at 11 37 58 AM Screenshot 2024-11-25 at 11 38 14 AM

@scottyaslan
Copy link
Contributor Author

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.

@rfellows please check these again as they should be working now.

@scottyaslan scottyaslan force-pushed the NIFI-13318 branch 2 times, most recently from 043e835 to 42ea7f0 Compare December 6, 2024 01:02
Copy link
Contributor

@mcgilman mcgilman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @scottyaslan! I've noted a few things below.

Copy link
Contributor

@mcgilman mcgilman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the updates @scottyaslan! I've noted a few more things below.

Copy link
Contributor

@mcgilman mcgilman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks again for the updates @scottyaslan! Looks great, will merge once CI completes.

@mcgilman mcgilman merged commit 0271e92 into apache:main Dec 10, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new ui Pull requests for work relating to the new user interface being developed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants