You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello!
Does the project need the ability to package generated source code to prevent namespace conflicts?
And each such package will have its own imports and dependencies among themselves, if necessary
I have already started doing this for my needs. If necessary, I can then make a pull request.
The text was updated successfully, but these errors were encountered:
Hello! Does the project need the ability to package generated source code to prevent namespace conflicts? And each such package will have its own imports and dependencies among themselves, if necessary
I have already started doing this for my needs. If necessary, I can then make a pull request.
Hello @zhorzh-p, can you share your implementation? I am having problem when generating my code and two different xsd files have same element name
I added a new flag 'multi' that separates the generated code into packages.
The program will require you to specify the names of all packages:
It will then split the code into the packages you specified:
And in the end, so that there are no conflicts between the created packages, you can create a go module: go mod init myservice
I'm also thinking of getting rid of manual entry of package names via a support config file. Also I haven't corrected/added tests yet. There are bugs and inaccuracies in the program which I will slowly correct.
Hello!
Does the project need the ability to package generated source code to prevent namespace conflicts?
And each such package will have its own imports and dependencies among themselves, if necessary
I have already started doing this for my needs. If necessary, I can then make a pull request.
The text was updated successfully, but these errors were encountered: