feat: update post in progress status when post changed (#2350)

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. 如果这是你的第一次,请阅读我们的贡献指南:<https://github.com/halo-dev/halo/blob/master/CONTRIBUTING.md>。
1. If this is your first time, please read our contributor guidelines: <https://github.com/halo-dev/halo/blob/master/CONTRIBUTING.md>.
2. 请根据你解决问题的类型为 Pull Request 添加合适的标签。
2. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request.
3. 请确保你已经添加并运行了适当的测试。
3. Ensure you have added or ran the appropriate tests for your PR.
-->

#### What type of PR is this?
/kind improvement
/area core
/milestone 2.0
<!--
添加其中一个类别:
Add one of the following kinds:

/kind bug
/kind cleanup
/kind documentation
/kind feature
/kind improvement

适当添加其中一个或多个类别(可选):
Optionally add one or more of the following kinds if applicable:

/kind api-change
/kind deprecation
/kind failing-test
/kind flake
/kind regression
-->

#### What this PR does / why we need it:
文章更新时 reconcile 文章内容是否有草稿正在编辑,有则更新status.inProgress=true否则为false
#### Which issue(s) this PR fixes:

<!--
PR 合并时自动关闭 issue。
Automatically closes linked issue when PR is merged.

用法:`Fixes #<issue 号>`,或者 `Fixes (粘贴 issue 完整链接)`
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
a part of #2322

#### Special notes for your reviewer:
/cc @halo-dev/sig-halo 
#### Does this PR introduce a user-facing change?

<!--
如果当前 Pull Request 的修改不会造成用户侧的任何变更,在 `release-note` 代码块儿中填写 `NONE`。
否则请填写用户侧能够理解的 Release Note。如果当前 Pull Request 包含破坏性更新(Break Change),
Release Note 需要以 `action required` 开头。
If no, just write "NONE" in the release-note block below.
If yes, a release note is required:
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".
-->

```release-note
None
```
pull/2365/head
guqing 2022-08-26 15:38:11 +08:00 committed by GitHub
parent a060c2ab17
commit 7682318ae6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 0 deletions

View File

@ -88,6 +88,7 @@ public class PostReconciler implements Reconciler<Request> {
}
// handle contributors
String headSnapshot = post.getSpec().getHeadSnapshot();
contentService.listSnapshots(Snapshot.SubjectRef.of(Post.KIND, name))
.collectList()
.subscribe(snapshots -> {
@ -102,6 +103,14 @@ public class PostReconciler implements Reconciler<Request> {
.sorted()
.toList();
status.setContributors(contributors);
// update in progress status
snapshots.stream()
.filter(snapshot -> snapshot.getMetadata().getName().equals(headSnapshot))
.findAny()
.ifPresent(snapshot -> {
status.setInProgress(!isPublished(snapshot));
});
});
// handle cancel publish,has released version and published is false and not handled
@ -149,4 +158,8 @@ public class PostReconciler implements Reconciler<Request> {
// TODO The default capture 150 words as excerpt
return StringUtils.substring(text, 0, 150);
}
private boolean isPublished(Snapshot snapshot) {
return snapshot.getSpec().getPublishTime() != null;
}
}