search

StydeNet / enlighten

Enlighten your APIs with auto-generated documentation
MIT License
575 stars 32 forks source link

export command errors to assets paths #44

Open alphyon opened 3 years ago

alphyon commented 3 years ago

Hi, I use a command to export in external documentation, the results, but when I pass a path to deploy, this generates a bad reference, the references take an absolute path and change the value in the config file but the bug persists, why the export files not take the styles but not take the reference the assets files

sileence commented 3 years ago

@alphyon If I understand the problem is in PATH to the assets of the preview content? If so, a trick I use for this is to change the APP_URL in the environment file before running the tests and generating the documentation, so it contains the correct body.

I'll think about this problem to see if I can implement a better solution.