feat(exclude-package-go-type): impl - #2081
Open
zdunecki wants to merge 2 commits into
Open
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
Copy link
Copy Markdown
Kusari Analysis Results:
No pinned version dependency changes, code issues or exposed secrets detected!
Found this helpful? Give it a 👍 or 👎 reaction! |
Sorry, something went wrong.
Copy link
Copy Markdown
|
Kusari PR Analysis rerun based on - db2c6aa performed at: 2025-09-05T20:24:10Z - link to updated analysis |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
It's a concept only but we need this at @livesession.
The case is like that:
Let's say we have a core structures defined schema.yaml in our core golang package and want to reuse that so we have to:
generate ./schema.yaml inside our core package
then in our api we need to import that schemas to our openapi and based on that schema generate a golang server too
We would like to have references to core instead of a new objects. Plus we want to have schema.gen.go inside core package.
Why it's needed? Because x-go-type overwrite what type is generated so using this method inside core package we would get types that does not exists. If we use that from api perspective (which use core it's fine cuz the references are already generated)