You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it should be possible to add links to images and the path should be flexible created depending on the place where the page is located.
Analog to translating [schemaname].[tablename] into the correct path
Current Behavior
I cant use relative path to images in markdown because the current folder of the generated html could be on a different path:
schema_abc
schema_abc/table_def
if a relative path is correct for one location it will be wrong for the other location
Possible Solution
the same issue is solved when using [schemaname].[tablename] or [tablename] in markdown: the generated path to the linked object is correct no matter where the document containing markdown is located.
Something similar is required for images.
For example there could be one folder containing the required images. Maybe D:\Tools\schemaspy\PerformanceAnalytics\images, maybe something different like D:\Tools\schemaspy\PerformanceAnalytics\customer_images
And in the markdown some special placeholder could be used, for example
![image 1]({imagefolder}\image_1.jpeg)
and this needs to be translated into a relativ path depending on the current folder
The idea could also be extended to use placeholders in a more general way. And a place is required where to define placeholders. Maybe program options are a simple way and compatible with the current configuration.
Or any other way which allow to store and use images inside the generated documentation.
The text was updated successfully, but these errors were encountered:
Expected Behavior
it should be possible to add links to images and the path should be flexible created depending on the place where the page is located.
Analog to translating [schemaname].[tablename] into the correct path
Current Behavior
I cant use relative path to images in markdown because the current folder of the generated html could be on a different path:
if a relative path is correct for one location it will be wrong for the other location
Possible Solution
the same issue is solved when using
[schemaname].[tablename]
or[tablename]
in markdown: the generated path to the linked object is correct no matter where the document containing markdown is located.Something similar is required for images.
For example there could be one folder containing the required images. Maybe
D:\Tools\schemaspy\PerformanceAnalytics\images
, maybe something different likeD:\Tools\schemaspy\PerformanceAnalytics\customer_images
And in the markdown some special placeholder could be used, for example
![image 1]({imagefolder}\image_1.jpeg)
and this needs to be translated into a relativ path depending on the current folder
The idea could also be extended to use placeholders in a more general way. And a place is required where to define placeholders. Maybe program options are a simple way and compatible with the current configuration.
Or any other way which allow to store and use images inside the generated documentation.
The text was updated successfully, but these errors were encountered: