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

fix: simple key handling upto 1024 chars. #1

Merged
merged 1 commit into from
Sep 8, 2024

Conversation

Prashansa-K
Copy link
Collaborator

Currently, if a key is >128 characters, it is
handled as a complex key mapping. This renders some OpenAPI spec paths invalid.
Until the same PR go-yaml#1037 is not accepted in the upstream repository,
we are adding the changes in this fork and will be using this in deck.

Fixes: Kong/go-apiops#198

Currently, if a key is >128 characters, it is
handled as a complex key mapping. This renders some
OpenAPI spec paths invalid.
Until the same PR go-yaml#1037
is not accepted in the upstream repository,
we are adding the changes in this fork and will be
using this in deck.

Fixes: Kong/go-apiops#198
@Prashansa-K Prashansa-K requested a review from Tieske September 6, 2024 05:56
Copy link
Member

@Tieske Tieske left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@Prashansa-K Prashansa-K merged commit 5e0ba55 into v3 Sep 8, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

deck file patch with path lengths > 128 characters
2 participants