I did some more testing that I’ll document in the next few days. I think the issue is that JSDOM has no concept of window.sessionStorage. Which ever process calls the function I wrote breaks with a Type Error undefined, but if the function is pulled out of the context of getInitialSettings it looks like we get an error specific to sessionStorage. I’ve tried pulling in some add’l npm packages meant to define storage elements, but haven’t had success yet. Then again, haven’t had bandwidth to try really hard yet.
Thanks Rob. More findings soon. Joshua Poore > On Aug 12, 2019, at 10:23 AM, Rob Foley <r...@apache.org> wrote: > > I looked through the branch/issue and tried playing around with the code a > bit. It seems like the userale script is not being added to the JSDom > environment. Our custom resourceLoader (found in test/testUtils.js) is > being ran, and is getting the correct content, however at some point JSDom > is not actually putting that content into the page. I tried downgrading > JSDom to an earlier version with no luck, so I am not sure if there is > something else going on. > >> On Sat, Aug 10, 2019 at 12:47 AM Joshua Poore <poor...@apache.org> wrote: >> >> Rob (or anyone else): >> >> any thoughts? >> >> issue: https://issues.apache.org/jira/browse/FLAGON-441 < >> https://issues.apache.org/jira/browse/FLAGON-441> >> >> branch: >> https://github.com/apache/incubator-flagon-useralejs/tree/FLAGON-434 < >> https://github.com/apache/incubator-flagon-useralejs/tree/FLAGON-434>
