Skip to content
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

Use undefined rather than void #240

Merged
merged 1 commit into from
Jan 14, 2022

Conversation

petebacondarwin
Copy link
Contributor

void should only be used for return types of functions that do not return anything (not even undefined).

See https://www.typescriptlang.org/docs/handbook/2/functions.html#void

`void` should only be used for return types of functions that do not return anything (not even undefined).

See https://www.typescriptlang.org/docs/handbook/2/functions.html#void
@changeset-bot
Copy link

changeset-bot bot commented Jan 14, 2022

⚠️ No Changeset found

Latest commit: 0a02120

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Member

@GregBrimble GregBrimble left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -112,15 +112,15 @@ export interface CfWorkerInit {
/**
* The name of the worker.
*/
name: string | void;
name: string | undefined;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we use name?: string as a shortcut?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

name?: string has a subtly different meaning, which is that the name property doesn't have to appear on the object, whereas name: string|undefined means that the property must appear on the object but it can be assigned undefined.

Since this interface is only used internally, and we always provide name, I would generally prefer to make the props explicit, to avoid bugs in the future where someone forgets to provide a prop, even though it was needed.

@petebacondarwin petebacondarwin merged commit 165ab70 into cloudflare:main Jan 14, 2022
@petebacondarwin petebacondarwin deleted the no-void branch January 14, 2022 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants