[typescript] fix GrayMatterOption.engines type

[stas-vilchik]

The current definition of GrayMatterOption.engines is not correct. string and object in this snippet are not types, but the parameter names. Their type is resolved as any.

engines?: {
  [index: string]:
    | ((string) => object)
    | { parse: (string) => object; stringify?: (object) => string }
}

The problem is that the TypeScript requires to always put parameter names.

[mysticflute]

any idea on when this can be pulled in?

[jaredwray]

I believe this is the same issue I am seeing. Parameter 'string' implicitly has an 'any' type. @jonschlinkert can we get this pulled in? Anyway we can help on this?

[Himenon]

I have the same problem.

[tstelzer]

Same here, please merge.

[EryouHao]

@jonschlinkert please merge, thanks.

[1999]

@jonschlinkert hey, this PR is more than half a year old and it's pretty much important for all TS users. Also, the project hasn't got any changes during the last half-year. What's the status of gray-matter project?

[robertmassaioli]

This change looks good to me. It has also been reported four times:

• This PR
• Fix typing issues #77
• fix invalid type definitions for engines option #84
• fix(types): add missing types #86

I'm going to merge it in and do a release when I gain release permission.

Also, hello everybody, I'm a new Contributor on a trial run and, if this goes well, I'll be looking to help make that Pull Requests are at-least initially reviewed within a 2-week period by a contributor to this repository and then are given the next steps to getting the PR merged in.

I am especially keen to see bugfixes be merged in and released.

I don't yet have access to release but, hopefully, will be able to do so soon. Cheers.