Update README.md

[chety]

• Enhance method implementation by returning in a single line rather than using if and else.
• Add support for the default parameter value.

[ljharb]

this isn't actually best - our linter config will warn on it. it'd be:

Suggested change

	//best
	inbox.filter(({ subject, author } ) => {
	return subject === 'Mockingbird' && author === 'Harper Lee';
	});
	//best
	inbox.filter(({ subject, author }) => subject === 'Mockingbird' && author === 'Harper Lee');

however, then we've defeated the whole point of this section, which is showing patterns around explicit return in callbacks.

so, i think this is best reverted.

[ljharb]

this shouldn't ever be a function, it should just be inline.

[ljharb]

Suggested change

	function getDefaultValueIfNotPresent(obj,defaultValue){
	return isNullOrUndefined(obj) ? defaultValue : obj;
	}
	function getDefaultValueIfNotPresent(obj,defaultValue) {
	return isNullOrUndefined(obj) ? defaultValue : obj;
	}

this is entirely unnecessary, though, since ?? exists - you can just do obj ?? defaultValue, without any need for a function.

[ljharb]

this is fine, but it may not actually be better - the "y" might add clarity, depending on what the code is doing.

[ljharb]

i don't think this adds anything over the existing example of function handleThings(opts = {}) {.

Suggested change

	function handleThings(opts = getDefaultValueIfNotPresent(opts,{})){
	// ...
	}

[chety]

If you explicitly pass null to handleThings function then opts will be null rather than the default {} value. Therefore I think we should also handle this case.