Skip to content

fix: for "typescript" mode, require object shorthand or index signatures #1012

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

Merged
merged 1 commit into from
Apr 11, 2023

Conversation

brettz9
Copy link
Collaborator

@brettz9 brettz9 commented Apr 10, 2023

fixes #1001

BREAKING CHANGE:

For typescript mode, one must use object shorthand or index signatures, e.g., {[key: string]: number} or {a: string, b: number}

…res; fixes gajus#1001

BREAKING CHANGE:

For typescript mode, one must use object shorthand or index signatures, e.g., `{[key: string]: number}` or `{a: string, b: number}`
@brettz9 brettz9 force-pushed the typescript-objects branch from d46b285 to 3d23782 Compare April 11, 2023 11:19
@brettz9 brettz9 merged commit f1ea352 into gajus:main Apr 11, 2023
@brettz9 brettz9 deleted the typescript-objects branch April 11, 2023 15:12
@github-actions
Copy link

🎉 This PR is included in version 41.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

In typescript mode, only allow {[key: string]: string} and not object<>, object.<>, Object<> and Object.<>
3 participants