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.

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

Add global parameters that apply to all paths #2357

Closed
costeaalex opened this issue Sep 21, 2020 · 5 comments
Closed

Add global parameters that apply to all paths #2357

costeaalex opened this issue Sep 21, 2020 · 5 comments

Comments

@costeaalex
Copy link

This is somewhat of an oversight by I think it would be a very handy thing to be able to define global custom headers (which is what I need and found a couple of others needing) and have them apply to all requests. Cluttering the paths with refs is not very maintainable nor efficient.

Thanks

@MikeRalphson
Copy link
Member

This is a duplicate of the (closed) issue #1577 - see ongoing discussions in OAI/Overlay-Specification#34 #1466 .

@costeaalex
Copy link
Author

costeaalex commented Sep 23, 2020

Mike, my nipples do not explode with delight as these issues don't seem to specifically address the global parameter problem. In one of them it's about grouped parameters and the other has shifted towards referenced parameters rather than global parameters so I am afraid this will fly under the radar and not really be clearly addressed. Am I wrong in assuming this?

I see in the ticket with global parameters the concern is with exceptions to requests for the global parameters but that one is closed and in the other ones there isn't talk of global parameters per se.

@MikeRalphson
Copy link
Member

@costeaalex I just wanted to point you at the issues flagged up when this was last raised in #1577 - it's unlikely the avenues being considered have changed since the last time it came up (i.e. global doesn't mean global all the time, and traits / groups of parameters are more in line with the way we see the spec. evolving in the future).

@Amilpuy
Copy link

Amilpuy commented May 19, 2023

对于大型项目而言,大量的$ref真的非常难以使用,不是我对业务模块拆分的还不够细,而是功能性的接口真的太多,就没有什么方式来支持all paths配置这类方式?en:(For large projects, a large amount of $ref is really difficult to use, not because I haven't broken down the business modules enough, but because there are too many functional interfaces, there is no way to support all paths configuration and other methods?),大量的Google之后我发现,对于Spring Boot 3.0+以上真的没有其它更好的选择,要么只能接受现状,要么进行大量的编码!(After a lot of Google, I found that there is really no better choice for Spring Boot 3.0+or above, either to accept the status quo or to do a lot of coding!)

@Amilpuy
Copy link

Amilpuy commented May 20, 2023

对于大型项目而言,大量的$ref真的非常难以使用,不是我对业务模块拆分的还不够细,而是功能性的接口真的太多,就没有什么方式来支持所有路径配置这类方式?en:(对于大型项目,大量的$ref确实很难用,不是因为我对业务模块分解的不够,而是因为功能接口太多,没有办法支持所有路径配置等方法?),大量的谷歌之后我发现,对于Spring Boot 3.0以上以上真的没有其它更好的选择,要么只能接受现状,要么进行大量的编码!(谷歌了很多之后,发现Spring Boot 3.0+以上真的没有更好的选择了,要么接受现状,要么做大量编码!)

now:Add global customizer and filters OAI/OpenAPI-Specification#1616

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants