customInfos - doesn't work when a json string is assigned to JEST_HTML_REPORTERS_CUSTOM_INFOS

[anandcbe14]

Describe the bug
customInfos - - doesn't work when the Key/Value Pairs object is stringified and assigned to process.env.JEST_HTML_REPORTERS_CUSTOM_INFOS in the globalSetup

To Reproduce
Steps to reproduce the behavior:

1. In the js for globalSetup, create a json object and assign it - viz.

const mycustInfo = { 'Environment':'dev',  'Browser':'chrome'  };
process.env.JEST_HTML_REPORTERS_CUSTOM_INFOS = JSON.stringify(mycustInfo);

and specify this in package.json:
"customInfos" : "JEST_HTML_REPORTERS_CUSTOM_INFOS"

2. Once the test is executed, the following warning message is displayed in console log:
   the value of Custom info env must be a json string point to an Object

3. However, when the customInfos is specified directly in package json as below, it works as expected:
   ``"customInfos" : [{ title: "Environment", value: "dev" }, { title: "Browser", value: "chrome" }]`

Expected behavior
Dynamically constructing the customInfos object as specified in #1 is expected to work as in #3.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Mac iOS13
• Browser: Chrome/Firefox/Safari
• Version: package versions 2.1.0 and above

Additional context
REF: #32 for the original feature request and impl.. of JEST_HTML_REPORTERS_CUSTOM_INFOS

Adjusting

jest-html-reporters/index.js

Line 40 in 841ce98

const infos = JSON.parse(JEST_HTML_REPORTERS_CUSTOM_INFOS);

` to
const infos = JSON.parse(customInfos); fixes the issue

[Hazyzh]

Thanks for reported and fixed the issue. will include this fix in the next version.

[Hazyzh]

Hi @anandcbe14, new version 2.1.3 which fixed this issue has been published. you can have a try, Thanks for reported.