url is marked required on react-select-fetch components. No it isn't. That isn't true.
Or, more specifically, it's only true iff get isn't overridden. Then it's... the url parameter that gets injected into your get method's first parameter. Whatever. My get method can easily hardcode that, and then I have to use one less prop. Or I would, if it wasn't marked as a required prop on the component.
Why don't we, as a compromise, mark url nullable and then say about here we do a runtime check to make sure we actually have a url or throw.
urlis marked required onreact-select-fetchcomponents. No it isn't. That isn't true.Or, more specifically, it's only true iff
getisn't overridden. Then it's... theurlparameter that gets injected into yourgetmethod's first parameter. Whatever. Mygetmethod can easily hardcode that, and then I have to use one less prop. Or I would, if it wasn't marked as a required prop on the component.Why don't we, as a compromise, mark
urlnullable and then say about here we do a runtime check to make sure we actually have aurlor throw.