-
Notifications
You must be signed in to change notification settings - Fork 87
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
Add quick filters on scenarios, simulations and atomic testing #1352
Conversation
885f93d
to
b3ea90e
Compare
d872957
to
2d2be72
Compare
@PostMapping(EXERCISE_URI + "/{exerciseId}/injects/simple") | ||
@PreAuthorize("isExerciseObserver(#exerciseId)") | ||
@Transactional(readOnly = true) | ||
public Iterable<InjectOutput> exerciseInjectsSimple( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it normal you keep the same API with pagination and not with pagination ? Can you merge the two or there is a reason that we keep the old one ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Originally the API endpoints of all entities returned the entire DB table and everything was stored at the store level.
Going through pagination improves performance to return a more restricted list.
Unfortunately, there is still a lot of code to migrate to use the new endpoints and not all of it can be done in this task. But it’s something to keep in mind!
openbas-api/src/main/java/io/openbas/rest/inject/ScenarioInjectApi.java
Outdated
Show resolved
Hide resolved
Comments taken into account. |
Proposed changes
Related issues