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

Remove severity classes 'bsi' #2434

Closed

Conversation

janowagner
Copy link
Member

@janowagner janowagner commented Sep 1, 2020

These classes are identical with the classes of 'nist' anyway.

dependabot bot and others added 30 commits July 16, 2020 09:48
…arn/gsa/testing-library/jest-dom-5.11.1

Bump @testing-library/jest-dom from 5.11.0 to 5.11.1 in /gsa
…arn/gsa/types/jest-26.0.5

Bump @types/jest from 26.0.4 to 26.0.5 in /gsa
…arn/gsa/i18next-19.6.2

Bump i18next from 19.6.0 to 19.6.2 in /gsa
…arn/gsa/downshift-5.4.7

Bump downshift from 5.4.6 to 5.4.7 in /gsa
…arn/gsa/types/jest-26.0.7

Bump @types/jest from 26.0.5 to 26.0.7 in /gsa
…arn/gsa/jest-junit-11.1.0

Bump jest-junit from 11.0.1 to 11.1.0 in /gsa
…arn/gsa/i18next-19.6.3

Bump i18next from 19.6.2 to 19.6.3 in /gsa
…arn/gsa/react-redux-7.2.1

Bump react-redux from 7.2.0 to 7.2.1 in /gsa
…arn/gsa/uuid-8.3.0

Bump uuid from 8.2.0 to 8.3.0 in /gsa
…arn/gsa/testing-library/jest-dom-5.11.2

Bump @testing-library/jest-dom from 5.11.1 to 5.11.2 in /gsa
…arn/gsa/qhistory-1.1.0

Bump qhistory from 1.0.3 to 1.1.0 in /gsa
…arn/gsa/babel/core-7.11.0

Bump @babel/core from 7.10.5 to 7.11.0 in /gsa
…arn/gsa/types/jest-26.0.8

Bump @types/jest from 26.0.7 to 26.0.8 in /gsa
@janowagner janowagner marked this pull request as ready for review September 1, 2020 22:00
@janowagner janowagner requested a review from a team September 1, 2020 22:00
saberlynx and others added 20 commits September 2, 2020 16:57
Refactor task details into function component
…arn/gsa/types/jest-26.0.13

Bump @types/jest from 26.0.12 to 26.0.13 in /gsa
…arn/gsa/storybook/react-6.0.21

Bump @storybook/react from 6.0.20 to 6.0.21 in /gsa
Ensure that the real timers are restore after running all the useTiming
tests. If the timers are not restored this may lead to strange bugs in
other tests.
If the timer value is undefined, null or smaler then zero no timer will
be started ad all. The timeoutValue can either be directly passed as
timeout value or as a return value from a timeout callback funktion.
With using hooks the reloadInterval (and also the other reload interval
values) are read from the gmp settings and not from the gmp object
directly. Therefore fix the mock in the details page tests.
These classes are identical with type 'nist' anyway.
@bjoernricks bjoernricks changed the base branch from master to gsa-21.04 September 4, 2020 07:23
@janowagner janowagner added the work in progress This pull request should not be merged yet, more commits are expected label Sep 6, 2020
@swaterkamp
Copy link
Member

Superseded by #2445

@swaterkamp swaterkamp closed this Sep 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
work in progress This pull request should not be merged yet, more commits are expected
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants