Open GoulartNogueira opened 1 year ago
I'm using a no-code web app builder called Bubble.io and the template came with feather icons installed. That's another reason why it's so hard to simply
@GoulartNogueira you may do that without any new features, just clone this repo, add your icons with any name you like, build custom feather icons and require it in your project form repo
something like that
npm i https://github.com/user_name/node_project_name
this will help you keep tracking your own feather Icons collection
Also looks like Feather Icons are dead, 😢 no activity since March 2022
@GoulartNogueira just take a look to this fork https://github.com/dsplce-co/feather-icons
and how @dsplce-co add new icons to feather https://github.com/dsplce-co/feather-icons/commit/7e476bd91dbaaa348c624ec9a2c1ee19ad7a88f4
Problem:
I'm using Feather Icons in a lot of elements in my application.
However (as most users here) now I really need a specific icon that is not among the original feather icons.
Solutions I thought:
(and why they're not great)
I could change my application, duplicating some elements to cover both cases (button_feather / button_svg). And that's not a best practice.
I could encapsulate feather icons in another "smart" element that accepts both feather or naive svg images. I could change all elements to make some try/exception. Or even quit feather and use another library. But that would be labor intensive, as it requires a lot of changes in my application.
Suggestion:
A feature to add my own custom icon at my local application. That solution would empower each user to solve their own problem. 90% of issues / pull requests are "icon request" and it seems like Feather will never accept most of them (for several reasons).
So even if my custom icon does not follow feather's best practices, I would only compromise my own application.
It looks we had a "Handle usage of custom icons" on the roadmap. But the roadmap was abandoned. https://github.com/feathericons/feather/commit/466b3f0494a39c286efd3271f7171be442a127f6
Next Steps:
What would require for us to enable this feature? Can I help on something?