-
Notifications
You must be signed in to change notification settings - Fork 28
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
@sapui5/ts-types-esm
- Opa5.waitFor
options.actions
should be optional
#306
Comments
Opa5.waitFor
options.actions
should be optional@sapui5/ts-types
- Opa5.waitFor
options.actions
should be optional
Thanks for your feedback. The TS support for the testing related APIs is still work in progress. BTW: did you also use the As you report quite some issues here, I am getting interested in how you are using the types? How are your projects setup? What toolchain do you use? Which IDE? And, really the classic Global types or the ESM types? Would it be possible for you to share some infos? 🙇♂️ |
@sapui5/ts-types
- Opa5.waitFor
options.actions
should be optional@sapui5/ts-types-esm
- Opa5.waitFor
options.actions
should be optional
@petermuessig thanks for the response! to be honest i'm not all that familiar with ui5, but since i'm good with typescript i'm helping a ui5 developer convert his project to typescript so there's probably quite a few things i'm doing wrong lol. to answer your questions:
mainly like the
i primarily use webstorm, but sometimes vscode
using const sManifestUrl = sap.ui.require.toUrl(_sAppModulePath + 'manifest.json') |
seems this is fixed in the latest version of |
@DetachHead thanks for your fast feedback and the answers for my questions. Some of the Globals can't be avoided easily unfortunately like |
it doesn't seem to be mandatory, see all the examples in the docs where
waitFor
is called without an actioni see where it's defined here but as far as i can tell the documentation in the source code doesn't appear to control whether the generated types are mandatory or not
The text was updated successfully, but these errors were encountered: