Skip to content

fix(Import v5): make parsing more tolerant to undefined values - #8509

Merged
gatzjames merged 4 commits into
Kong:developfrom
gatzjames:feature/import-v5-optional-values
Mar 24, 2025
Merged

gatzjames merged 4 commits into
Kong:developfrom
gatzjames:feature/import-v5-optional-values

Conversation

@gatzjames

@gatzjames gatzjames commented Mar 24, 2025 •

Copy link
Copy Markdown
Contributor

Highlights:

  • Allow for more values to be undefined when parsing v5 imports

Closes INS-5218

@gatzjames
gatzjames requested a review from a team March 24, 2025 10:00
@gatzjames gatzjames self-assigned this Mar 24, 2025
@gatzjames
gatzjames force-pushed the feature/import-v5-optional-values branch from b1d8dee to 7d3e9dd Compare March 24, 2025 11:54
jackkav
jackkav previously approved these changes Mar 24, 2025
@gatzjames
gatzjames force-pushed the feature/import-v5-optional-values branch from a5d9040 to 2187146 Compare March 24, 2025 14:23
@gatzjames
gatzjames merged commit c4b513e into Kong:develop Mar 24, 2025
@gatzjames
gatzjames deleted the feature/import-v5-optional-values branch March 24, 2025 14:42
cwangsmv pushed a commit that referenced this pull request Apr 21, 2025
* make parsing more tolerant to undefined values

* move collection to it's own schema

* add more restrictions to the collection union types to make sure parsing is correct

* update ts checks
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.

2 participants