-
Notifications
You must be signed in to change notification settings - Fork 39
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 files in subfolders not rendered in Maker software #6
Comments
Just tested this on a Windows 10 machine. I can't seem to reproduce the issue you're having. On my end, files in subfolders open with no issues. |
In my case it doesn't load OS: Windows 10 Enterprise 22H2 (64-bit) |
If the file/folder lives in your filesystem, the app should have no issues opening it. @m-p-3 does the app load files within subdirectories that are not located on Google Drive for you? |
If I copy the same directory structure into another location (ie: Documents) Marker will load the .md files in subfolders just fine. If it's on the mapped G Drive, they won't load. |
Tested 1.2.0, still unable to show the content of MD files when they're stored in the G: networked Google Drive. |
@m-p-3 I just tested using a folder that is synced w/ Google Drive, and it works well in Marker with no issues. My guess is that your Google Drive folder in not mounted in your file system, so it can't be accessed using normal file system APIs. |
Issue Submission
Problem Description
Maker software fails to open Markdown files located within subfolders of the Project directory. For example, while
doc1.md
renders successfully,doc2.md
located within a subfolder fails to display any content.Steps to Reproduce
Expected Behavior
Markdown files located within subfolders should be opened and displayed in Maker as expected, similar to files located in the root directory of the Project.
Actual Behavior
Markdown files located within subfolders fail to display any content when opened in Maker.
Screenshots (Optional)
N/A
Environment Information
Additional Information
N/A
The text was updated successfully, but these errors were encountered: