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 (29,106 stars) (8,513 forks)batch import
area/seatacontribution welcomegood first issuehelp wanted

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

Tech stack
java
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaSpring Boot autoconfigurationSeata
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the autoconfiguration properties in the seata module of spring cloud alibaba. Look at existing default property definitions in the codebase, such as in SeataAutoConfiguration classes. Identify which properties can be simplified by setting defaults. Review the comments in the issue for any suggestions from maintainers.