Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: release v0.9.0 #1109

Merged
merged 22 commits into from
May 10, 2024
Merged

chore: release v0.9.0 #1109

merged 22 commits into from
May 10, 2024

Conversation

alice-yyds
Copy link
Contributor

No description provided.

FGYFFFF and others added 22 commits February 6, 2024 18:40
@FGYFFFF
refactor: client query enum
ad3f359
@FGYFFFF
chore: merge back v0.8.1 (#1068)
c6927c4 
#### What type of PR is this?
<!--
Add one of the following kinds:

build: Changes that affect the build system or external dependencies
(example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes:
Travis, Circle, BrowserStack, SauceLabs)
docs: Documentation only changes
feat: A new feature
optimize: A new optimization
fix: A bug fix
perf: A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style: Changes that do not affect the meaning of the code (white space,
formatting, missing semi-colons, etc)
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries
such as documentation generation
-->

#### Check the PR title.
<!--
The description of the title will be attached in Release Notes, 
so please describe it from user-oriented, what this PR does / why we
need it.
Please check your PR title with the below requirements:
-->
- [ ] This PR title match the format: \<type\>(optional scope):
\<description\>
- [ ] The description of this PR title is user-oriented and clear enough
for others to understand.
- [ ] Attach the PR updating the user documentation if the current PR
requires user awareness at the usage level. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)


#### (Optional) Translate the PR title into Chinese.


#### (Optional) More detailed description for this PR(en: English/zh:
Chinese).
<!--
Provide more detailed info for review(e.g., it's recommended to provide
perf data if this is a perf type PR).
-->
en:
zh(optional):

#### (Optional) Which issue(s) this PR fixes:
<!--
Automatically closes linked issue when PR is merged.
Eg: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

#### (Optional) The PR that updates user documentation:
<!--
If the current PR requires user awareness at the usage level, please
submit a PR to update user docs. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)
-->
@FGYFFFF
Merge branch 'develop' into refactor/client_query_enum
9d07631
@li-jin-gou
optimize: filter shortConnErr in tracer (#1037)
1f9997c
@GuangmingLuo
chore: update readme images and documentation (#1075)
f91ce33
@XiaoYi-byte
Increased unit test coverage for pkg/protocol/header_test (#1074)
81f0c83
@kingcanfish
feat: add SetHandlers when fast fail for no valid host and invalid rP…
b7cbc9d 
…ath (#1057)
@FGYFFFF
feat: add more default type
4742b2e
@FGYFFFF
feat: add more default type for binding (#1056)
3b3296c 
#### What type of PR is this?
<!--
Add one of the following kinds:

build: Changes that affect the build system or external dependencies
(example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes:
Travis, Circle, BrowserStack, SauceLabs)
docs: Documentation only changes
feat: A new feature
optimize: A new optimization
fix: A bug fix
perf: A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style: Changes that do not affect the meaning of the code (white space,
formatting, missing semi-colons, etc)
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries
such as documentation generation
-->
feat
#### Check the PR title.
<!--
The description of the title will be attached in Release Notes, 
so please describe it from user-oriented, what this PR does / why we
need it.
Please check your PR title with the below requirements:
-->
- [ ] This PR title match the format: \<type\>(optional scope):
\<description\>
- [ ] The description of this PR title is user-oriented and clear enough
for others to understand.
- [ ] Attach the PR updating the user documentation if the current PR
requires user awareness at the usage level. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)


#### (Optional) Translate the PR title into Chinese.
为参数绑定提供更多的默认类型支持

#### (Optional) More detailed description for this PR(en: English/zh:
Chinese).
<!--
Provide more detailed info for review(e.g., it's recommended to provide
perf data if this is a perf type PR).
-->
en: 为参数绑定提供更多的默认类型支持
zh(optional): add more default type for binding

- 增加了 map、struct、slice 等类型的默认值处理
- 降低 default value 的优先级，避免在做完 json.unmarshal() 后，default value 将其值覆盖

#### (Optional) Which issue(s) this PR fixes:
<!--
Automatically closes linked issue when PR is merged.
Eg: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

#### (Optional) The PR that updates user documentation:
<!--
If the current PR requires user awareness at the usage level, please
submit a PR to update user docs. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)
-->
@lafer-fz
fix: import alias index "
9858163
@FGYFFFF
Merge branch 'develop' into refactor/client_query_enum
3bc1be6
@FGYFFFF
refactor(hz): client query enum (#1064)
0285a34 
#### What type of PR is this?
<!--
Add one of the following kinds:

build: Changes that affect the build system or external dependencies
(example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes:
Travis, Circle, BrowserStack, SauceLabs)
docs: Documentation only changes
feat: A new feature
optimize: A new optimization
fix: A bug fix
perf: A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style: Changes that do not affect the meaning of the code (white space,
formatting, missing semi-colons, etc)
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries
such as documentation generation
-->
refactor
#### Check the PR title.
<!--
The description of the title will be attached in Release Notes, 
so please describe it from user-oriented, what this PR does / why we
need it.
Please check your PR title with the below requirements:
-->
- [x] This PR title match the format: \<type\>(optional scope):
\<description\>
- [x] The description of this PR title is user-oriented and clear enough
for others to understand.
- [x] Attach the PR updating the user documentation if the current PR
requires user awareness at the usage level. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)


#### (Optional) Translate the PR title into Chinese.
重构 client query 对于 enum 传递的配置形式

#### (Optional) More detailed description for this PR(en: English/zh:
Chinese).
<!--
Provide more detailed info for review(e.g., it's recommended to provide
perf data if this is a perf type PR).
-->
en: Refactoring the client query's configuration form for enum
zh(optional): 重构 client query 对于 enum 传递的配置形式

#### (Optional) Which issue(s) this PR fixes:
<!--
Automatically closes linked issue when PR is merged.
Eg: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

#### (Optional) The PR that updates user documentation:
<!--
If the current PR requires user awareness at the usage level, please
submit a PR to update user docs. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)
-->
@FGYFFFF
fix(hz): template import alias (#1093)
bd2a9b2 
#### What type of PR is this?
<!--
Add one of the following kinds:

build: Changes that affect the build system or external dependencies
(example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes:
Travis, Circle, BrowserStack, SauceLabs)
docs: Documentation only changes
feat: A new feature
optimize: A new optimization
fix: A bug fix
perf: A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style: Changes that do not affect the meaning of the code (white space,
formatting, missing semi-colons, etc)
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries
such as documentation generation
-->
fix

#### Check the PR title.
<!--
The description of the title will be attached in Release Notes, 
so please describe it from user-oriented, what this PR does / why we
need it.
Please check your PR title with the below requirements:
-->
- [x] This PR title match the format: \<type\>(optional scope):
\<description\>
- [x] The description of this PR title is user-oriented and clear enough
for others to understand.
- [x] Attach the PR updating the user documentation if the current PR
requires user awareness at the usage level. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)


#### (Optional) Translate the PR title into Chinese.
fix customized template import alias error

#### (Optional) More detailed description for this PR(en: English/zh:
Chinese).
<!--
Provide more detailed info for review(e.g., it's recommended to provide
perf data if this is a perf type PR).
-->
en:
zh(optional): customized template import alias error

#### (Optional) Which issue(s) this PR fixes:
<!--
Automatically closes linked issue when PR is merged.
Eg: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

#### (Optional) The PR that updates user documentation:
<!--
If the current PR requires user awareness at the usage level, please
submit a PR to update user docs. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)
-->
@FGYFFFF
optimize: router_sort
637e0da
@FGYFFFF
optimize: router sort
9a95dc8
@FGYFFFF
optimize(hz): sort route strictly which preventing sorting inconsiste…
6f62cd9 
…ncies (#921)

#### What type of PR is this?
<!--
Add one of the following kinds:

build: Changes that affect the build system or external dependencies
(example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes:
Travis, Circle, BrowserStack, SauceLabs)
docs: Documentation only changes
feat: A new feature
optimize: A new optimization
fix: A bug fix
perf: A code change that improves performance
refactor: A code change that neither fixes a bug nor adds a feature
style: Changes that do not affect the meaning of the code (white space,
formatting, missing semi-colons, etc)
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries
such as documentation generation
-->
optimize
#### Check the PR title.
<!--
The description of the title will be attached in Release Notes, 
so please describe it from user-oriented, what this PR does / why we
need it.
Please check your PR title with the below requirements:
-->
- [x] This PR title match the format: \<type\>(optional scope):
\<description\>
- [x] The description of this PR title is user-oriented and clear enough
for others to understand.
- [ ] Attach the PR updating the user documentation if the current PR
requires user awareness at the usage level. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)


#### (Optional) Translate the PR title into Chinese.
对路由进行严格排序，防止生成代码出现大量的 diff

#### (Optional) More detailed description for this PR(en: English/zh:
Chinese).
<!--
Provide more detailed info for review(e.g., it's recommended to provide
perf data if this is a perf type PR).
-->
en: Strict ordering of routes to prevent generating code with lots of
diffs
zh(optional): 对路由进行严格排序，防止生成的路由代码出现由于顺序带来的 diff
之前的路由在排序的时候漏掉三个case:
- "/:b/a": 这种情况会取 ":b" 与其他节点进行比较，导致路由生成不是按照路由首字母来排序
- "get /a", "post /a": 这种情况之前默认使用 "a" 和 "a" 进行比较，导致生成的路由 get/post
等方法可能出现不一致的顺序，从而生成代码出现 diff
- 之前构建路由树的时候，结构和用户定义接口的顺序有关，导致用户添加一个接口时，生成代码顺序发生变化，针对这个情况也做了排序
- 之前漏掉对于中间节点的排序(路由组节点的排序)，导致可能会出现生成代码的diff

本 pr 的修改不会影响路由注册的逻辑，但是会使得之前生成的路由代码的顺序发生改变(在idl的method特别多的时候表现明显)。
在这个问题修好之后，以后所以的 idl 都不会对 router 带来diff(除了加路由)

#### (Optional) Which issue(s) this PR fixes:
<!--
Automatically closes linked issue when PR is merged.
Eg: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

#### (Optional) The PR that updates user documentation:
<!--
If the current PR requires user awareness at the usage level, please
submit a PR to update user docs. [User docs
repo](https://github.com/cloudwego/cloudwego.github.io)
-->
@Haswf
feat: Add Partitioned Parameter to SetCookie (#1048)
b5b3f9d
@welkeyever
feat: add method to exile requestContext (#1101)
2d13882
@FGYFFFF
fix: router sort (#1107)
a80eadb
@wzekin @Duslia
fix: resp set trailer will panic (#1102)
cbd63c6 
Co-authored-by: yinxuran.lucky <[email protected]>
@FGYFFFF
chore(hz): release v090 (#1105)
ed4a8d8
@alice-yyds
chore: update version v0.9.0
617fad8
@alice-yyds alice-yyds requested review from a team as code owners May 10, 2024 08:14
@li-jin-gou li-jin-gou merged commit 8bb1346 into main May 10, 2024
24 checks passed
@li-jin-gou li-jin-gou deleted the release-v0.9.0 branch May 10, 2024 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@FGYFFFF FGYFFFF FGYFFFF approved these changes

@Duslia Duslia Duslia approved these changes

@wzekin wzekin wzekin approved these changes

@welkeyever welkeyever welkeyever approved these changes

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.