@latch i’m sorry if you feel there’s wasted time here, some of this is as you’re blazing a trail here. which is massively useful in terms of shining a light on what’s missing.
What I recall is you trying to use the browser native
safe api to instantiate an app and then call
safe.fetch(<url>). That would get your data without any CORS issues.
Though that in itself is more JS app level than using yew, which I know is what you’re aiming for here. It may be you could use the rust safe-api for this in your code directly. Though I’m not sure at all if this will compile for wasm. It may be worth a try though.
I’ve made this branch
https://github.com/joshuef/safe_browser/tree/AccessControlHeaderBranch and you can see the commit here to enable this. I think should get us around the CORS issue.
In general @latch if you feel the APIs aren’t intuitive or are missing something as you’re developing. We’re super open to feedback. You can feel free to raise an RFC much as @shane has done for missing apis over here so we can improve / add anything missing. HTTP responses, naming etc are all valid topics to be getting in to