Vitaly Puzrin
Vitaly Puzrin
I mean renderer functions. Those can not be empty (to show demo, for example), but there is no way to provide universal solution. So, users are expected to customize those.
I don't like to promote api options for things, which are expected to be changed.
At first glance, i have no ideas how to add aria labels without options or hardcoding english phrases. Both are not perfect. So, right now i see no ways how...
I don't like to hardcode english texts. My position is to change nothing if good solution is not available.
As i explained, common mistake is to consider default renderer as out-of-box solution. But it is not. As soon as you accept this fact, you will fine to tune it...
> Should I open an issue? If you wish to discuss ideas - yes. Issue is much better place for such things.
Example with aria-label override can be added here https://github.com/markdown-it/markdown-it-footnote#use. I this case, hardcoded english phrase will be ok. If code change wished - anyone can inspect declined PRs/issues and suggest...
1. Policy to leave all for customization is intended, to not poison api with zillion of rare options. 2. Refer to added value for "many users" should have concrete proofs....
This PR contains a lot of formatting garbadge. I don't see real changes. Please remove everything, not related to your proposal.
IMO result of proposed option can be solved by simple renderer functions override. We try to keep options as minimal as possible for such case, to keep api clean.