larksuite / larksuite/oapi-sdk-java
是否支持可配置cache前缀
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 310
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
如AppTicketManager中的
private static final String APP_TICKET_PREFIX = "app_ticket";
与TokenManager中的
private static final String appAccessTokenKeyPrefix = "app_access_token";
private static final String tenantAccessTokenKeyPrefix = "tenant_access_token";
现在只能在创建client后，手动重置自定义的
ICache cache = LocalCache.getInstance();
GlobalAppTicketManager.setAppTicketManager(new AppTicketManager(cache));
GlobalTokenManager.setTokenManager(new TokenManager(cache));
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting AppTicketManager, TokenManager, GlobalAppTicketManager, and GlobalTokenManager, focusing on the hard-coded cache key prefixes and the client setup shown in the issue. Determine how configuration can be exposed without manually replacing the global managers; done means callers can set custom prefixes through the supported client configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100