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

[GUI] Jump directly to documentation url without error modal #3974

Merged
merged 1 commit into from
Sep 13, 2023

Conversation

cservakt
Copy link
Collaborator

@cservakt cservakt commented Aug 9, 2023

Currently on the report detail page there is a red error bubble where we can click on the checker documentation button to have more information about the error. The button click triggers a modal that contains already known information and the real checker documentation URL.
The modal is unnecessary and it has two steps to navigate to the effective documentation. To reduce the step numbers, there are some modifications in the Report and the ReportStepMessage components.
When the report page is loaded the first thing is to create an errorChecker, then getting its documentation and passing it to ReportStepMessage via props. The ReportStepMessage component present the checker documentation button if the URL exists. The button refers to the checker error documentation without displaying a modal. When the documentation is not available, the ReportStepMessage shows the "No documentation for checker." message in the bubble.

@cservakt cservakt added WIP 💣 Work In Progress GUI 🎨 documentation 📖 Changes to documentation. labels Aug 9, 2023
@cservakt cservakt added this to the release 6.23.0 milestone Aug 9, 2023
@Szelethus Szelethus self-requested a review August 14, 2023 14:41
Copy link
Collaborator

@Szelethus Szelethus left a comment

Choose a reason for hiding this comment

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

Nice, welcome to CodeChecker! :)

I recently left a comment in another PR that summarized what I usually like to see in the summary of the patch:
#3949 (comment)
Yours is currently empty, so please fill it out.

Copy link
Collaborator

@Szelethus Szelethus left a comment

Choose a reason for hiding this comment

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

You seem to have forgotten to add a newline in between the title of your commit and the message of the commit, which results in the entire summary to be in fact your title. This is the output of git log --oneline:
image

edit: I tried this PR out, and it works fine for me, but I lack the expertise on this part of the codebase to comment anything substantial :)

@@ -25,18 +25,17 @@ module.exports = {

"show documentation" (browser) {
const reportDetailPage = browser.page.reportDetail();
const dialog = reportDetailPage.section.documentationDialog;
reportDetailPage.expect.element('@showDocumentationBtn').to.be.present.before(5000, false);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Seems like we try to fit lines in 79 columns in the rest of the file as well -- could you add a newline?

@@ -313,8 +308,7 @@ import ReportTreeKind from "@/components/Report/ReportTree/ReportTreeKind";
import { SetCleanupPlanBtn } from "@/components/Report/CleanupPlan";

import AnalysisInfoBtn from "./AnalysisInfoBtn";
import CheckerDocumentationDialog from
"@/components/CheckerDocumentationDialog";
Copy link
Collaborator

Choose a reason for hiding this comment

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

Does this mean that we can just outright delete that file? Seems like only Report.vue used it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

No, we cannot delete it. The Reports.vue also uses the CheckerDocumentationDialog.

@Szelethus Szelethus changed the title Jump directly to documetaion url without error modal [GUI] Jump directly to documetaion url without error modal Aug 16, 2023
@cservakt cservakt changed the title [GUI] Jump directly to documetaion url without error modal [GUI] Jump directly to documentation url without error modal Aug 16, 2023
@@ -73,7 +79,8 @@ export default {
index: { type: [ Number, String ], default: null },
bus: { type: Object, default: null },
prevStep: { type: Object, default: null },
nextStep: { type: Object, default: null }
nextStep: { type: Object, default: null },
docUrl: { type: String, default: "" }
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a minor comment, but "not having some kind of information" could be represented by null like in case of the other members. docUrl could be changed accordingly in this ReportStepMessage.vue and Report.vue file tool.

Currently on the report detail page there is a red error bubble where we can click on the checker documentation button to have more information about the error. The button click triggers a modal that contains already known information and the real checker documentation URL.
The modal is unnecessary and it has two steps to navigate to the effective documentation. To reduce the step numbers, there are some modifications in the Report and the ReportStepMessage components.
When the report page is loaded the first thing is to create an errorChecker, then getting its documentation and passing it to ReportStepMessage via props. The ReportStepMessage component present the checker documentation button if the URL exists. The button refers to the checker error documentation without displaying a modal. When the documentation is not available, the ReportStepMessage shows the "No documentation for checker." message in the bubble.
Copy link
Collaborator

@Szelethus Szelethus left a comment

Choose a reason for hiding this comment

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

LGTM!

@Szelethus Szelethus merged commit 96a40a6 into Ericsson:master Sep 13, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation 📖 Changes to documentation. GUI 🎨 test ☑️ Adding or refactoring tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants