January 17, 2023, 10:24am
I would love to build myself a local dashboard that sources data from Logseq.
Unfortunately, HTTP API disallows CORS and there is no setting to change that.
It would be awesome if we could tweak the value of the
Access-Control-Allow-Origin header for the HTTP API.
effect: true to the manifest should work?
I wrote this plugin and tested it locally before publishing to the marketplace. Installed from the marketplace a single one of its features won’t work due to cross-frame issues. Installed via Load unpacked plugin it works just fine. If you toggle your Developer Tools open in Logseq with this plugin, installed from the marketplace, you’re sure to notice the failing top.document line.
This was my second attempt on what should be an easy feature. The first attempt is here:
My dilemma is w…
11:45AM - 15 Mar 22 UTC
Agenda is run using lsp protocol. This results in a request For a Google Calenda
… r URL CORS error.
Setting effect to true looks like can solve this problem.
Sorry that this is not likely fine documented
April 8, 2023, 1:07pm
I can understand how that could work within a plugin, but I am looking to call the API from outside of Logseq - ideally, a locally hosted page.
But maybe if I package it as a plugin, that could work