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
Hi...!
I wanted to suggest a small enhancement that could make the bot even more useful. Currently, when the bot unzips a file and uploads the contents , it doesn't indicate the directories or subdirectories the files originally belonged to. This will be difficult to understand the original structure of the archive file.
Would it be possible to add a feature that preserves and indicates the directory structure of the files when they are uploaded? This way, users can easily identify which files belong to which directories or subdirectories.
The text was updated successfully, but these errors were encountered:
this will be part of the big rework of the bot
not only the directory origin will be displayed on files caption, but when uploading you will be able to see the structure and navigate into it, so you can granularly choose which files/folders to upload
Thankyou for your response ,the ability to navigate through the directory structure with buttons sounds great..
In the meantime, could you please implement a simpler solution where the directory origin is displayed as a caption when uploading the files? This small enhancement would be temporary improvement while the more complex navigation feature is being developed.
Hi...!
I wanted to suggest a small enhancement that could make the bot even more useful. Currently, when the bot unzips a file and uploads the contents , it doesn't indicate the directories or subdirectories the files originally belonged to. This will be difficult to understand the original structure of the archive file.
Would it be possible to add a feature that preserves and indicates the directory structure of the files when they are uploaded? This way, users can easily identify which files belong to which directories or subdirectories.
The text was updated successfully, but these errors were encountered: