[redux-actions@2.3.0] More specific definitions

[alexey-pelykh]

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change. (Run with npm test.)
• Follow the advice from the readme.
• Avoid common mistakes.
• Run npm run lint package-name (or tsc if no tslint.json is present).

Select one of these and delete the others:

If adding a new definition:

• The package does not already provide its own types, or cannot have its .d.ts files generated via --declaration
• If this is for an NPM package, match the name. If not, do not conflict with the name of an NPM package.
• Create it with dts-gen --dt, not by basing it on an existing project.
• tslint.json should be present, and tsconfig.json should have noImplicitAny, noImplicitThis, strictNullChecks, and strictFunctionTypes set to true.

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes: <>
• Increase the version number in the header if appropriate.
• If you are making substantial changes, consider adding a tslint.json containing { "extends": "dtslint/dt.json" }.

If removing a declaration:

• If a package was never on DefinitelyTyped, you don't need to do anything. (If you wrote a package and provided types, you don't need to register it with us.)
• Delete the package's directory.
• Add it to notNeededPackages.json.

[typescript-bot]

@alexey-pelykh Thank you for submitting this PR!

🔔 @jaysoo @alexgorbatchev @alechill - please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

If no reviewer appears after a week, a DefinitelyTyped maintainer will review the PR instead.

[typescript-bot]

After 5 days, no one has reviewed the PR 😞. A maintainer will be reviewing the PR in the next few days and will either merge it or request revisions. Thank you for your patience!

[ghost]

This will still match basically everything though -- false would match for example.

[alexey-pelykh]

Very true, on one hand that's useless, on other hand, returned object is not a string after all

[alexey-pelykh]

Super-open for suggestions, that is

[ghost]

If this interface is meant to be created by the library and not by the user, you could add a _combinedActionType: void field to make this a pseudo-nominal interface.

[alexey-pelykh]

Like this?

export interface CombinedActionType {
    _dummy: undefined;
    toString(): string;
}

[ghost]

Yeah -- at that point toString is unnecessary since it's inherited from Object anyway:

interface I {}
function f(i: I): string { return i.toString(); } // No error

[alexey-pelykh]

@Andy-MS, done!

[ghost]

Thanks!