Skip to content

[Improvement-18249][DAO] Route AlertGroupMapper and AccessTokenMapperaccess through repository Dao#18261

Open
ruanwenjun wants to merge 1 commit into
apache:devfrom
ruanwenjun:dao/alert-group-and-access-token
Open

[Improvement-18249][DAO] Route AlertGroupMapper and AccessTokenMapperaccess through repository Dao#18261
ruanwenjun wants to merge 1 commit into
apache:devfrom
ruanwenjun:dao/alert-group-and-access-token

Conversation

@ruanwenjun
Copy link
Copy Markdown
Member

Was this PR generated or assisted by AI?

YES, gpt 5.5

Purpose of the pull request

Introduce AlertGroupDao and AccessTokenDao so the api layer depends only on the repository abstraction. The two mappers are bundled because UsersServiceImpl and ResourcePermissionCheckServiceImpl share both.

AlertGroupDao preserves the mapper's custom ORDER BY update_time DESC in queryAllGroupList (cannot be replaced with IDao.queryAll). existGroupName returns primitive boolean via Boolean.TRUE.equals so callers drop the == Boolean.TRUE dance.

AccessTokenDao renames mapper.selectAccessTokenPage to queryAccessTokenPage and mapper.deleteAccessTokenByUserId to deleteByUserId. updateById in AccessTokenServiceImpl switches from int to boolean so the guard becomes !success instead of i <= 0.

AlertGroupControllerTest.clear() replaces the BaseMapper.delete(QueryWrapper) idiom with a queryAllGroupList stream + deleteById loop so the controller test can stop reaching into MyBatis-Plus internals.

Tracking issue: #18249

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.

(or)

This pull request is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(or)

Pull Request Notice

Pull Request Notice

If your pull request contains incompatible change, you should also add it to docs/docs/en/guide/upgrade/incompatible.md

@ruanwenjun ruanwenjun added improvement make more easy to user or prompt friendly refactor labels May 14, 2026
@ruanwenjun ruanwenjun added this to the 3.4.2 milestone May 14, 2026
@ruanwenjun ruanwenjun force-pushed the dao/alert-group-and-access-token branch 6 times, most recently from 0ec0921 to 0ac5d7b Compare May 18, 2026 14:41
… access through repository Dao

Introduce AlertGroupDao and AccessTokenDao so the api layer depends only
on the repository abstraction. The two mappers are bundled because
UsersServiceImpl and ResourcePermissionCheckServiceImpl share both.

AlertGroupDao preserves the mapper's custom ORDER BY update_time DESC in
queryAllGroupList (cannot be replaced with IDao.queryAll). existGroupName
returns primitive boolean via Boolean.TRUE.equals so callers drop the
== Boolean.TRUE dance.

AccessTokenDao renames mapper.selectAccessTokenPage to queryAccessTokenPage
and mapper.deleteAccessTokenByUserId to deleteByUserId. updateById in
AccessTokenServiceImpl switches from int to boolean so the guard becomes
!success instead of i <= 0.

AlertGroupControllerTest.clear() replaces the BaseMapper.delete(QueryWrapper)
idiom with a queryAllGroupList stream + deleteById loop so the controller
test can stop reaching into MyBatis-Plus internals.

Tracking issue: apache#18249
@ruanwenjun ruanwenjun force-pushed the dao/alert-group-and-access-token branch from 0ac5d7b to fb27155 Compare May 19, 2026 08:52
@sonarqubecloud
Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 60%)

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend improvement make more easy to user or prompt friendly refactor test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant