Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Markdown content not statically rendered #397

Closed
2 tasks
zawasp opened this issue May 18, 2023 · 2 comments · Fixed by #415
Closed
2 tasks

Markdown content not statically rendered #397

zawasp opened this issue May 18, 2023 · 2 comments · Fixed by #415
Labels
bug Something isn't working

Comments

@zawasp
Copy link
Contributor

zawasp commented May 18, 2023

Please provide the environment you discovered this bug in.

@analogjs/content: "^0.2.0-beta.8",
@analogjs/router: "^0.2.0-beta.7",
@analogjs/platform: "^0.2.0-beta.7"

Which area/package is the issue in?

content

Description

When prerendering static markdown routes, the generated html file does not contain the rendered markdown content. Instead, the markdown angular component is present in the generated html file.

See the repo at https://github.com/zawasp/analogjs-test and the served content from dist/analog/public at https://analogjs-test.pages.dev/about. The About markdown page source contains <analog-markdown ngh="0"><div class="analog-markdown"></div></analog-markdown> instead of the markdown content.

Please provide the exception or error you saw

No response

Other information

No response

I would be willing to submit a PR to fix this issue

  • Yes
  • No
@zawasp zawasp added the bug Something isn't working label May 18, 2023
@henriquecustodia
Copy link
Contributor

Same here

@brandonroberts
Copy link
Member

I think I know what's going on here. The template for the internal markdown component isn't being compiled in the library, so we may need to adjust the compilation mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants