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

[Importers] OpenAPI and Swagger use underscore-dot syntax for environment variables #5807

Conversation

Asamsig
Copy link
Contributor

@Asamsig Asamsig commented Feb 27, 2023

changelog(Fixes): Fixed an issue where environment variables generated by OpenApi and Swagger importers now use underscore-dot syntax, instead of custom variable access.

Change environment variables generated by OpenApi and Swagger importers to use underscore-dot syntax, instead of custom variable access.

@filfreire filfreire requested a review from a team March 1, 2023 16:29
@filfreire filfreire force-pushed the fix-importers-not-using-underscore-syntax-environment-variables branch from 2a852b9 to 812a04c Compare March 3, 2023 13:47
@filfreire
Copy link
Member

@Asamsig can you help us remember what was the motive behind this PR? Sorry in advance for not remembering.

…rs to use underscore-dot syntax, instead of custom variable access.
@filfreire filfreire force-pushed the fix-importers-not-using-underscore-syntax-environment-variables branch from 812a04c to 3286cc0 Compare March 30, 2023 10:30
@Asamsig
Copy link
Contributor Author

Asamsig commented Mar 30, 2023

Hi @filfreire , it started from this Slack message: https://getinsomnia.slack.com/archives/C3BBF236C/p1674209107398529.

It is mostly a cosmetic change.

Currently imported variables from a swagger/openapi spec will look like this:
image

Since it doesn't use the underscore-syntax, the option show variable source and value doesn't trigger, instead it shows as a custom variable.

@filfreire filfreire enabled auto-merge March 31, 2023 10:17
@filfreire filfreire disabled auto-merge March 31, 2023 10:27
@filfreire filfreire enabled auto-merge March 31, 2023 10:54
@filfreire filfreire added this pull request to the merge queue Mar 31, 2023
Merged via the queue into Kong:develop with commit e2d672a Mar 31, 2023
@filfreire
Copy link
Member

@Asamsig you can claim a free tshirt for this PR contribution - find more at https://konghq.com/community/open-source-contribution

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