[useAutocomplete] CreateFilterOptionsConfig is not optional in CreateFilterOptions

[alaumh]

• The issue is present in the latest release.
• I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

From useAutocomplete.d.ts

export type CreateFilterOptions = (
  config: CreateFilterOptionsConfig,
) => (option: any, state: FilterOptionsState) => any[];

export const createFilterOptions: CreateFilterOptions;

From useAutocomplete.js

export function createFilterOptions(config = {}) {
 ...
}
const defaultFilterOptions = createFilterOptions();

Expected Behavior 🤔

Make CreateFilterOptionsConfig optional

export type CreateFilterOptions = (
  config?: CreateFilterOptionsConfig,
) => (option: any, state: FilterOptionsState) => any[];

export const createFilterOptions: CreateFilterOptions;

Steps to Reproduce 🕹

Steps:

Context 🔦

Your Environment 🌎

Tech	Version
Material-UI	v4.?.?
React
Browser
TypeScript
etc.

[oliviertassinari]

@alaumh Thank you for raising this inconsistency issue. I'm wondering. What's your use case for using createFilterOptions without any arguments (the default)? Thanks

[alaumh]

@oliviertassinari Thanks for the reply. Currently no, I found this inconsistency when I was studying the source code through converting the implementation to typescript.

[oliviertassinari]

@alaumh Ok, I think that we should update the TypeScript definition. Do you want to handle it? :)

[alaumh]

@oliviertassinari I woud love to do it, will submit a PR later. Thanks!