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

Investigate if gRPC Auto-gateway can try the canonical gateway first for registered modules #23368

Open
Tracked by #23188
technicallyty opened this issue Jan 14, 2025 · 0 comments
Open
Tracked by #23188

Investigate if gRPC Auto-gateway can try the canonical gateway first for registered modules #23368

technicallyty opened this issue Jan 14, 2025 · 0 comments
Assignees
@technicallyty
Labels
C:server/v2 Issues related to server/v2

Comments

@technicallyty
Copy link
Contributor

No description provided.

@technicallyty technicallyty mentioned this issue Jan 14, 2025
Open
4 tasks
@github-actions github-actions bot added the needs-triage Issue that needs to be triaged label Jan 14, 2025
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Cosmos-SDK Jan 14, 2025
@technicallyty technicallyty changed the title Possibly keep manual grpc gateway support for third party modules by having catch-all handler be first/last (to verify) handler (so manual registration overrides catch-all handler) Investigate if gRPC Auto-gateway can try the canonical gateway first for registered modules Jan 14, 2025
@technicallyty technicallyty reopened this Jan 14, 2025
@technicallyty technicallyty self-assigned this Jan 14, 2025
@technicallyty technicallyty added C:server/v2 Issues related to server/v2 and removed needs-triage Issue that needs to be triaged labels Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@technicallyty technicallyty

Labels
C:server/v2 Issues related to server/v2
Projects
Cosmos-SDK
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@technicallyty