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
Instead of bundling the list of supported file type icons, I believe it would be more convenient to modify the list of supported icons from a remote place, have the plugin fetch the mapping as a JSON file from some static URL, cache that locally, and base icon name resolution on that. With this, it wouldn't be required to package a new release simply for an added icon.
A suitable location would be a JSON file in the default branch, where it would double-serve as an automatically semi-up-to-date fallback for packaged releases (readable via sublime.load_resource).
The text was updated successfully, but these errors were encountered:
Sounds like a great idea. Not sure how to get a remote resource (since I haven't done much with sublime packages) but this would work better than making a patch release on every update. Feel free to PR if you want since I might be too busy to focus on this.
I don't have a personal interest in this as I don't use the package and have much higher priority issues, so don't count on me for a PR. I just noticed through my notifications that the last couple releases were only icon additions.
Instead of bundling the list of supported file type icons, I believe it would be more convenient to modify the list of supported icons from a remote place, have the plugin fetch the mapping as a JSON file from some static URL, cache that locally, and base icon name resolution on that. With this, it wouldn't be required to package a new release simply for an added icon.
A suitable location would be a JSON file in the default branch, where it would double-serve as an automatically semi-up-to-date fallback for packaged releases (readable via
sublime.load_resource
).The text was updated successfully, but these errors were encountered: