flexsurfer
commented
7 years ago hi @timgilbert , thank you for the report, I'm using Odinodin/data-frisk-reagent library for render data, so i created the issue in his repo, maybe he can help
Closed timgilbert closed 6 years ago
flexsurfer
commented
7 years ago hi @timgilbert , thank you for the report, I'm using Odinodin/data-frisk-reagent library for render data, so i created the issue in his repo, maybe he can help
Hi. I'm storing a datascript connection object in my app-db in a re-frame project, and when I try to expand the app-db key in re-frisk, I get the following console errors (see below).
A datascript connection is arguably not the sort of thing one should properly store in the app-db, since it's more of a stateful component than pure data. Nonetheless, it would be nice if re-frisk didn't throw an error when trying to display it. I could imagine two potential workarounds. The best behavior might be for the re-frisk bits that render a string for each key in the app-db to catch exceptions, log them to the browser, and emit like
"##ERROR##"as the value in the shell.The quicker workaround would maybe be for the library user to pass in a list of keys to skip over in the app-db via the
:re-friskconfig key or the config map passed to(enable-re-frisk!).My project is in a bit of a messy state right now, but let me know if providing sample code to reproduce would be helpful. Thanks!