-
Notifications
You must be signed in to change notification settings - Fork 67
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
[Feature request]: Allow multiple thumbnail / assets paths #484
Comments
I understand the need to support thumbnails for assets not only in
In this approach, we also need to support functionality to remove or edit one of multiple paths. At this point we would require a GUI like the Ideally, all models are hosted on Fuel with thumbnails uploaded and we implement some mechanism to preview thumbnails of assets on Fuel. Something like this was already implemented by @luca-della-vedova in our rmf_site project. |
Yap to add on to @Yadunund's comment I expect most upcoming feature development to happen on the |
Good to hear the process on rmf_site! Is there a PR I can reference for this feature? |
Yes, the PR is linked in the original comment. |
Before proceeding, is there an existing issue or discussion for this?
Description
It seems that right now the thumbnails only allow 1 path. Allowing more paths should help with third-party or creating custom thumbnails that can be maintained in another repo, or for customer sensitive thumbnails.
I think this will be helpful especially I want to upload the demo I did here a long time ago with custom assets to be available instead of upload a lot of extra picture here, those assets are quite specific to the demo and might not be relevant to the use case that other people is using traffic editor for.
Implementation Considerations
I suggest something like
which is similar to a
$PATH
or add in an add button to add in multiple lines of input to add in more path.
Alternatives
No response
Additional information
If this feature is something that the maintainer also thinks is useful. I would gladly help to make a Pull Request.
The text was updated successfully, but these errors were encountered: