fix(gatsby-source-wordpress): Remove search and replace regex literal recommendation

[jooola]

A regular expression literal generate a RegExp object at compile time. We need to allow string or object in the option schema.

EDIT: I decided to remove the documentation entry recommending a Regex literal, instead of the above solution.

Improvements can be made in the future.

cc @TylerBarnes

Related Issues

Fix #31411
Related to #31091

[jooola]

@TylerBarnes Using Joi.alternatives() does not play well with the documentation, what should we do ?

I could add some extra code in the docs generation script, or force somehow the type to be a String, but using trueType in the meta did not work.

Any ideas ? Thoughts ?

Maybe this should be a blocker, before the searchAndReplace feature is released to the public as stable.

[jooola]

Does gatsby generate a graphql schema for the plugin options, and make it accessible from graphql ? If yes this means we cannot use Joi.alternatives ?

Should we simply remove the sentence saying we recommend regex expression literal ?

[jooola]

I finally simply removed the documentation string saying a regular expression literal was recommended.

[jooola]

Commited your change, rebased, should be good to go.

[TylerBarnes]

Thanks @jooola !

[jooola]

My pleasure