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

Show status mesage if a visualisation is closed due to engine error. #6937

Conversation

MichaelMauderer
Copy link
Contributor

@MichaelMauderer MichaelMauderer commented Jun 2, 2023

Pull Request Description

  • Adds a mechanism to propagate status messages through the app.
  • Adds a status messages when a visualisation is closed through an engine error.
Peek.2023-06-02.15-16.mp4

Important Notes

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

  • The documentation has been updated, if necessary.
  • Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
  • All code follows the
    Scala,
    Java,
    and
    Rust
    style guides. In case you are using a language not listed above, follow the Rust style guide.
  • All code has been tested:
    • Unit tests have been written where possible.
    • If GUI codebase was changed, the GUI was tested when built using ./run ide build.

Adds a status messages when a visualisation is closed through an engine error.
@MichaelMauderer MichaelMauderer added the CI: No changelog needed Do not require a changelog entry for this PR. label Jun 2, 2023
@MichaelMauderer MichaelMauderer self-assigned this Jun 2, 2023
@MichaelMauderer MichaelMauderer marked this pull request as ready for review June 2, 2023 14:29
Comment on lines 231 to 233
error!("Visualization {} failed to attach: {error}.", visualization.id);
model.handle_controller_failure(&failure_endpoint, visualization.expression_id);
let message =
format!("Failed to open visualization because of an error: {error}.");
Copy link
Contributor

Choose a reason for hiding this comment

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

The {error} messages should already have a dot at the end.

@@ -245,11 +255,17 @@ impl Visualization {
"Visualization {} failed to be modified: {error}. Will hide it in GUI.",
desired.id
);
let message =
format!("Failed to modify visualization because of an error: {error}.");
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
format!("Failed to modify visualization because of an error: {error}.");
format!("Failed to modify visualization because of an error: {error}");

@farmaazon
Copy link
Contributor

QA: 🟢

@MichaelMauderer MichaelMauderer added the CI: Ready to merge This PR is eligible for automatic merge label Jun 6, 2023
…n_visualisation_closes_because_of_engine_error

# Conflicts:
#	app/gui/src/presenter/graph/visualization.rs
@mergify mergify bot merged commit 86724cb into develop Jun 6, 2023
@mergify mergify bot deleted the wip/MichaelMauderer/Add_error_message_when_visualisation_closes_because_of_engine_error branch June 6, 2023 12:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: No changelog needed Do not require a changelog entry for this PR. CI: Ready to merge This PR is eligible for automatic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants