My situation seems reasonably common, I have a schema file that
contains a bunch of types and other schema files that define api calls
that include and reference the common types schema.
When I run source generator the first time it generates all the classes
for the included file, then if I move onto another schema it complains
that the common types have already been generated.
I see two ways around this, either I put each set of generated classes in
their own package/directory or I use the force flag to just ignore the
warnings and potentially miss other important warnings.
Neither of these seems right to me, is there a third way that makes more
sense like perhaps creating a parent schema file that references my
various schemas so that I'm only running source generator once?
Thanks,
Alex.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
