https://web.dev/samesite-cookies-explained

does it affect shadow-cljs' built in HTTP server?

Chrome Canary has this issue. Although it affects on cookies mostly. Just feel quite annoying

Hey guys! May you can help me... I'm not able to got a React component working with Shadow-cljs... I think it may something with the way I need to import... On the samples, the import is made that way:

import * as WebDataRocksReact from './webdatarocks.react';

["webdatarocks" :as wdr]

<WebDataRocksReact.Pivot />

[:> wdr/Pivot {}]

[:> wdr/WebDataRocksReact {}] 

I think this "." (dot) in import as well on component name is what troubles me...

@gleisonsilva try shadow-cljs browser-repl and then (require '["webdatarocks" :as wdr]) + (js/console.dir wdr)

in the browser console you should see the object and inspect it further

if there is a Pivot property then wdr/Pivot should work

Hey @thheller, there isn't...

hmm thats just a function

do you maybe need to instantiate it?

the docs don't tell that https://www.webdatarocks.com/doc/integration-with-react/ https://github.com/WebDataRocks/pivot-react/blob/master/src/App.js

Do you have some suggestion on how can I instantiate it?

you need this file also https://github.com/WebDataRocks/pivot-react/blob/master/src/webdatarocks.react.js

this isn't in the npm package so I guess they expect you to write this yourself?

probably best to skip the JS version and just write it directly in reagent

componentDidMount() {
			var config = {};
			config.container = ReactDOM.findDOMNode(this);
			this.parseProps(config);
			this.webdatarocks = new window.WebDataRocks(config);
		}

this seems to be the relevant part

Right. I'll try! Thk u very much!

@thheller looking through the code, I can see that the webdatarocks.js has the react parts

There is a way to import like in the example, like "webdatarocks.react"??

yuck

the ./webdatarocks.react import is a local import

it is not in the npm package

but it appears to export those to a global object if the global React exists

which is bad practice. the package in general doesn't seem very high quality

import * as WebDataRocksReact from './webdatarocks.react'; is just importing ./webdatarocks.react.js relative to the App.js

you can maybe access js/WebDataRocksReact if there is a global js/React (which there normally isn't)

Got it. I'll try the other way so...

Tks