-
Notifications
You must be signed in to change notification settings - Fork 61
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
Add generated models and factories types #225
Add generated models and factories types #225
Conversation
59c916f
to
cb3980a
Compare
fe2e929
to
5aa2dee
Compare
5aa2dee
to
9e81035
Compare
eba75e9
to
75a9abf
Compare
74f3a88
to
63e65b4
Compare
cb6968b
to
f52ad1a
Compare
/** | ||
* THIS FILE IS AUTO-GENERATED - SEE CONTRIBUTOR DOCUMENTATION | ||
*/ |
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.
This does raise an issue - these files are autogenerated, yes? Can we add a comment to that extent? I lost a day recently in another codebase editing a generated file and it is not fun to discover.
Or are the Factories not generated?
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.
Handlebars files are not autogenerated but they contain this banner so it gets into generated .d.ts
and .js
files. This template is deleted because there seem to be no need in having index file for model types.
It makes sense to have it for for JS files so all models can be imported into GeneratedClient using Node syntax and referenced in methods bodies. For type definitions we import model types that are referenced by methods signatures explicitly.
Thanks for mentioning this - it looks like some of templates do not have warning banner included - going to fix that.
e20069a
to
e66f50b
Compare
templates/factory.d.ts.hbs
Outdated
@@ -0,0 +1,21 @@ | |||
/*! |
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.
nit: we probably can get rid of the banners from the templates as we already have logic to handle it in one place (https://github.com/okta/okta-sdk-nodejs/blob/master/package.json#L14)
LGTM! Please squash the commits when merge to the upper-level branch. |
75a9abf
to
5484cab
Compare
* to be switched to Client in the downnstream branch
… do not re-export model types
… return type into imports
8b81ec3
to
34d57b7
Compare
add generated models and factories types (#225) * WIP on generating TS type declarations for operations * add templates for type files and add template helper functions * move typings to src/types * re-use signature getter for models and generated client * add types index and remove unused templates * unify export syntax * reduce blocklisted models filtering duplication * export model types * add factories templates and push generated model types * switch to named model exports * actually run eslint on templates dir * set proper return type for Collection and mark optional arguments * mark read-only properties * do default export models along with named export * expose Client type and add missing types * add re-generated models and remove manually-generated types * restore array type value and read-only modifier * bring models named export back * generate factories types * export GeneratedClient * to be switched to Client in the downnstream branch * specify correct types for Model constructor arguments * import Client for all models * remove default exports from models * remove models and factories index template * add extra newline for generated models, remove indents from type map, do not re-export model types * move eslint target for templates to downstream branch * add missing 'autogenerated' warning banner to templates * remove extra whitespaces, regenerate files * parametrize Collection return type in generated files * include generic type into imports list and re-generate types * preserve non-optinal query parameters * correct return type to be Response instead of undefined, include CRUD return type into imports * CR: remove copyright banners from templates Add type definitions for core objects, add typescript-eslint-plugin + tsd (re-opened) (#230) * WIP on generating TS type declarations for operations * WIP on adding types for core objects * update type references in core objects * WIP on adding types for core objects * update type references in core objects * run typescript-eslint on src/types * WIP on fixing ts-lint errors * represent object type as Record<string, unknown> * define RequestOptions type * define more specific type for core objects * add basic tsd test * install @types/node-fetch types * specify sourceType: module for types eslint config * add more tsd assertions * complete basic coverage for core object types assertions * include tsd run into test target * export types matching code exports * fix syntactic error in command * fix indents and apply basic eslint rules to definitions files * parametrize Collection type definition * list known config properties, update jwt function return type * widen type for cache middleware next function * replace MemoryStore references with CacheStorage * extract IRequestExecutor interface, make MemoryStore parameters optional * allow request executors w/o event emission * correct types for collection subscribers * CR: cascade eslint configuration * fix revealed eslint errors * move type tests to a separate directory * CR: break down type tests * add type assertions for generated client methods * use named import for Response * allow imports for create and delete operations only * remove unused import * fix rebase artifact remove irrelevant changes update changelog entry for 4.5.0 OKTA-373751 <<<Jenkins Check-In of Tested SHA: 1013098 for [email protected]>>> Artifact: okta-sdk-nodejs
Thanks for working on this. Any plans to release the types as part of the published SDK? The latest version 4.5.0 as of Apr 5, 2021 does not ship with types even though it is referenced in the package manifest @oleksandrpravosudko-okta |
Hey @oleksandrpravosudko-okta this was my fault. I just updated to |
Is it possible to make accessible externally, the User class? Trying to import from
|
Hi @theseyi - types that are imported 'outside' of index.d.ts can not be used in Unfortunately, there is an issue with generated client's method signatures (some methods expect model instances to be passed which should not be the case). I am working on getting those fixed and will release a new version afterwards - sorry for inconvenience. |
I see, thanks for clarifying @oleksandrpravosudko-okta. I was looking at the example you provided and on line1:
Thanks for looking into this |
@theseyi please check out 4.5.1 release. There is a short section in 4.5 README describing the suggested usage.
Unless I am misunderstanding the question, |
I thought I saw |
@theseyi Right, imports from |
Resolves of OKTA-241753
Promise<Collection>
toCollection
for model methods and generated clientPromise<undefined>
toPromise<Response>
for model methods and generated client