-
-
Notifications
You must be signed in to change notification settings - Fork 737
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
TypeScript typings errors for ScenarioConfig.config
and FeatureConfig.config
#4848
Comments
@danielrentz Please make Pull Request to fix this! |
@DavertMik |
@DavertMik This happens when I follow the steps in CONTRIBUTING.md:
After that, I tried with optional deps, which brings me a few steps further, but still no success:
Any advice? |
@DavertMik Even committing fails:
followed by a ton of unrelated (?) type linter errors |
@danielrentz well, looks like we need to run |
In https://codecept.io/advanced/#dynamic-configuration it is documented that
Scenario().config
can be called with(options)
,(string, options)
, or(function)
.The type signature in
types.d.ts
iswhich allows
(string)
,(options)
,(string, options)
, or(options, options)
. The function variant is missing completely.Better signature would be
(with the correct type for the test object).
Similar but even worse problem for
Feature().config
: Documentation only shows(options)
, buttypes.d.ts
containsBtw, in v3.6.10 the type definition of
FeatureConfig.config
was equal toScenarioConfig.config
, what was the reason for changing it?The text was updated successfully, but these errors were encountered: