Providing option.keys[] field with RegExp throws kp.slice() is not a function about json-2-csv

[mrodrig]

Hi @dwarthen-tnn, thanks for reporting this. The error that you're seeing (TypeError: kp.slice is not a function) is because the package doesn't currently support any RegExps in the keys option. As noted in the README, the keys option currently just supports either an array of strings or objects in this format:

{
  "field": string, // required
  "title": string, // optional
  "wildcardMatch": boolean, // optional - default: false
}

If I'm understanding your use case correctly, you're essentially looking for a way to specify a custom title for some keys while still including all of the auto-detected keys in the generated CSV. Is that accurate? If so, I think this should be possible to support by refactoring how the titles are specified. That seems like it's probably the best way to handle this type of use case, and could also be setup to handle the title prefixing for wildcardMatched keys desired in #247 too.

[dwarthen-tnn]

Hi @dwarthen-tnn, thanks for reporting this. The error that you're seeing (TypeError: kp.slice is not a function) is because the package doesn't currently support any RegExps in the keys option. As noted in the README, the keys option currently just supports either an array of strings or objects in this format:

I think my confusion arose because VS code was assuring me that RegExp was a valid type for the field property, but today I'm not able to replicate that or find any place in the types definitions where that could have come from.

If I'm understanding your use case correctly, you're essentially looking for a way to specify a custom title for some keys while still including all of the auto-detected keys in the generated CSV. Is that accurate?

Yes, that's essentially it. I've worked around this on my end by changing the titles of those fields in my code before they reach the Converter. Not ideal for my use case but it works OK.

Thank you for your reply!