Closed vanillajonathan closed 2 years ago
Firstly, this is a project I maintain in my free time next to my day job. I look at all the issues and PRs, some take longer to look through and make a decision for. Please allow me the time for that.
Secondly, I'm not seeing the use of this change. Sure it makes a neat little variable containing all icons, but ends up being more code for the exact same effect. I rather like the current look of the toolbarBuiltInButtons
variable as it shows how users can add their own custom buttons.
This PR serves as the underlying foundation for the next step.
Which is:
options.iconClassMap = extend({}, iconClassMap, options.iconClassMap || {});
Which allows integrators to easily use other icon sets without having to recreate every button themselves.
Then build what you want to build and provide the completed thing as a PR. Smaller increments through PRs only increase the risk of half finished functionality ending up in the source code.
Can this be merged?
I would prefer the iconClassMap
to use the name
property of the toolbar buttons because that is what the toolbar
option uses as well.
Alright, done.
Hi @Ionaru, this PR was made for exactly what? because it keeps doing the same effect, you can't change the icons even after this changes.
The https://github.com/Ionaru/easy-markdown-editor/pull/501 looks like really fix this. Please take a look in it!
@willGabrielPereira This PR was never meant to let you change the icons, it was just a refactor and a stepping stone to later expose it as options. See the comment https://github.com/Ionaru/easy-markdown-editor/pull/454#issuecomment-1133860132 above.
@Ionaru Please merge!