Raphael Wegmueller
Raphael Wegmueller
> > `` > > what's wrong with this ? The expected output of that would be ```html Lorem ipsum: dolor ``` > but then it's broken. there are no...
What about forbidding leading empty lines? So this ```md --- class: bla foo: bar --- ``` would become YAML but ```md --- hey: you --- ``` would become HTML
Acknowledged. It shouldn't be possible to leave `org` or `site` empty in the editor.
@yugandhar02 as far as I can see, you can `await` both functions. They resolve their promise once the element is loaded: - https://github.com/adobe/aem-boilerplate/blob/main/scripts/aem.js#L223 - https://github.com/adobe/aem-boilerplate/blob/main/scripts/aem.js#L248 In any case, this code...
@trieloff your PR does not address the original issue: a 401/403 response from the pipeline is plain text, not HTML, in which case the meta tag does not get injected....
We could try adding HTML that is identical to the DOM that Chrome adds when rendering the page, so the sidekick could still [recognize the 401/403 page](https://github.com/adobe/aem-sidekick/blob/main/src/extension/app/store/app.js#L1178-L1189) and act accordingly.
> I'd be grateful for pointers. Here's a pointer: https://github.com/adobe/aem-sidekick/blob/main/src/extension/auth.js#L112 Currenty, the sidekick only injects the `authorization` header with the transient site token if the tab URL matches a `aem.page`...
@trieloff sidekick v7.20.1 is published