-
Notifications
You must be signed in to change notification settings - Fork 56
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
tools/importer-rest-api-specs
: splitting the dataapigeneratorjson
package into transforms and stages
#3831
tools/importer-rest-api-specs
: splitting the dataapigeneratorjson
package into transforms and stages
#3831
Conversation
…epository models out into it's own package This both makes the migration to the new models simpler (since it's contained within one package) but also means the parent package can be tidied per Phase 10
…o split the transforms and file writing This both enables reuse (for graph in time) and allows us to switch over to the Data API SDK models
…m wasn't pulled out for a CSV type
…n` package to split the Generator and Transform stages
eaef0a7
to
45db742
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
} | ||
|
||
// NOTE: `Parent` types don't get a `TypeHintIn` or `TypeHintValue` | ||
// meaning that only |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this comment missing a bit 🤔 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is (it's a lift and shift) - but this is actually fixed in one of the follow up PR's so I'm gonna leave this for now
This PR refactors the
dataapigeneratorjson
package in two ways:resourcemanager
types into thedataapimodels
types) into it's own package (transforms
).filesystem
type (similar to how theimporter-msgraph-metadata
logic works) - the intention here is to allow both testability (since we can validate the files exist at the paths we're expecting more easily) and that this type can be reused when loading the data from disk too.This PR also makes the indentation consistent across all of the generated API Definitions - which means that when this PR is merged the regeneration is going to be fairly large but will only contain whitespace - but means that the API Definitions are consistent going forwards.
This PR represents a preparation stage for Phase 9 and 10 of #3754