Is your feature request related to a problem? Please describe.
The editors are not completely perfect. There might be cases missing which might be special to certain websites.
Describe the solution you'd like
Having the option to output the current content to a command and continue to use its outputs might be a powerful way around this.
77 might just be command: jq .something
189 is currently stalled because there is no great way to debug it. Having an output only command in between could be neat here: debug: <filepath> could just output the current state of whatever the input is. #189 also highlights that there might be some additional element required as just a file path would override itself on multiple runs of the same editor. Maybe don't take a file path and just write files with a counter in the name? It's just to help debug after all, not to be committed (maybe error on --commit when a debug editor is there?).
The docs of the command editor could include a hint to submit an issue about it. When its useful it could be added to the editor implementations natively.
Also, it can be searched for instances of this via GitHub search and implement it when I find a good case of this.
Is your feature request related to a problem? Please describe.
The editors are not completely perfect. There might be cases missing which might be special to certain websites.
Describe the solution you'd like
Having the option to output the current content to a command and continue to use its outputs might be a powerful way around this.
77 might just be
command: jq .something189 is currently stalled because there is no great way to debug it. Having an output only command in between could be neat here:
debug: <filepath>could just output the current state of whatever the input is. #189 also highlights that there might be some additional element required as just a file path would override itself on multiple runs of the same editor. Maybe don't take a file path and just write files with a counter in the name? It's just to help debug after all, not to be committed (maybe error on--commitwhen a debug editor is there?).The docs of the command editor could include a hint to submit an issue about it. When its useful it could be added to the editor implementations natively. Also, it can be searched for instances of this via GitHub search and implement it when I find a good case of this.