alibaba/spring-cloud-alibaba

[Optimize] Optimizing autoconfiguration properties in seata

Open

#3,756 opened on Jun 6, 2024

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Java (8,513 forks)batch import
area/seatacontribution welcomegood first issuehelp wanted

Repository metrics

Stars
 (29,106 stars)
PR merge metrics
 (Avg merge 8d 14h) (3 merged PRs in 30d)

Description

lQLPJyEW4dOLql3NAz3NBBWwkUdzf-PIcfQGMwDXk0eSAA_1045_829

As shown in the figure, this part of the configuration is relatively redundant compared to the integration of spring cloud alibaba, we can remove these configuration items by setting the default properties to simplify the yml configuration.

Contributor guide

Research direction
Find the autoconfiguration properties in the Seata integration module and identify which properties are redundant. Set default values in the code to remove the need for explicit YML configuration.
Tech stack
javaspring
Domain
backendcloud
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaGitSpring
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80