JamesBrill
commented
3 years ago Hi @ajw-m Thank you for the contribution. Some comments:
- Generally speaking, I try to only merge generic changes that will benefit a significant portion of the consumers of this library. This is motivated by keeping the library small and simple. At first glance, this appears to be a somewhat niche feature, so I'd like to understand what use case you had in mind for it. One that comes to mind is of a user dictating a long speech and wanting to edit their mistakes afterwards.
- Regarding the feature itself, it may be better exposed to consumers as a callback like
resetTranscript. Then they don't have to use commands to make use of this functionality, being able to trigger the backspace on any event, not just matched commands. - I suspect it would be possible to achieve the same thing outside the library by maintaining a separate state for the text being rendered and/or some creative use of
resetTranscript. If so, perhaps you could contribute a "recipe" showing consumers of this library how they could achieve that in a new Markdown file. This is something I've wanted to do for a while - aRECIPES.mdwith common use cases.
backspaceCommandlets the user backspace (delete the last word of the string)