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

Update web userguide #1706

Merged
merged 1 commit into from
Aug 15, 2018
Merged

Update web userguide #1706

merged 1 commit into from
Aug 15, 2018

Conversation

csordasmarton
Copy link
Contributor

No description provided.

@csordasmarton csordasmarton added the documentation 📖 Changes to documentation. label Aug 10, 2018
@csordasmarton csordasmarton added this to the release 6.8 milestone Aug 10, 2018
@csordasmarton csordasmarton requested a review from gyorb August 10, 2018 11:44
control paths, i.e. through different function calls. By checking
**Unique reports** a report appears only once even if it is found on several
paths.
The same bug may appear several times if it is found on different control paths,
Copy link
Contributor

Choose a reason for hiding this comment

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

execution path instead of control path?

@@ -180,6 +180,8 @@ run or by opening "diff view" between two runs then the following filter options
are available:
- [**Unique reports**](#userguide-unique-reports) - You can uniqueing the
reports by checking this.
- **Report hash** - Every report has a unique (hash) identifier called Unique
Report Identifier (RI) which can be filtered by using this input box.
Copy link
Contributor

Choose a reason for hiding this comment

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

URI instead of RI?

@@ -299,6 +311,18 @@ We are mapping checker names to different severity levels:
(E.g. _core.DivideZero, core.NullDereference, cplusplus.NewDelete, etc._)
- <span class="customIcon icon-severity-critical"></span> **Critical**

## <a name="userguide-manage-source-components"></a> Manage source components
Source components are named collection of directories specified as directory
Copy link
Contributor

Choose a reason for hiding this comment

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

What do you think about rephrasing the first sentence to something like this: Source components are named collections of directory filters.

Maybe a link to the directory filter documentation would be nice here.

@gyorb gyorb merged commit f76d676 into Ericsson:master Aug 15, 2018
@csordasmarton csordasmarton deleted the update-userguide branch September 11, 2018 08:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation 📖 Changes to documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants