apolloconfig/apollo

提交失败建议回到编辑界面

Open

#2,830 opened on Dec 10, 2019

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Java (10,177 forks)batch import
feature requesthelp wanted

Repository metrics

Stars
 (29,769 stars)
PR merge metrics
 (Avg merge 4d 13h) (6 merged PRs in 30d)

Description

相关问题和重现步骤

  1. A、B两人同时编辑一个配置
  2. A提交了编辑内容
  3. B提交时，提示编辑失败，然后直接跳到当前配置内容，导致B的修改丢失

期望 B提交编辑失败，提示失败原因，保持在编辑界面，让B可以复制下来编辑内容

Contributor guide

Research direction
Investigate Apollo's concurrent edit handling. Look for optimistic locking or version control in the configuration update flow. Trace the code path from submission to failure handling.
Tech stack
java
Domain
backendapi
Issue type
Bug
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
GitJavaApollo basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60