Open aaronrothschild opened 4 years ago
cc @grundleborg @lieut-data - I can't imagine that storing 2 versions of the Post (if modified by the plugins from the original) is acceptable overhead, but I may be wrong if all we need is the text.
Something else to consider, probably even less imaginable in our current architecture would be a PostWillBeServed
(BeforeGetPost
?) hook, and then GetPostUnprocessed
for editing the original contents.
I can sort of see an argument to treat the MessageWillBePosted
as an edit event, not unlike if the user had edited their own post. This would store the "original message" in a referenced, deleted post, and make it accessible with somewhat minimal overhead. It's not quite the right paradigm, of course, but in terms of overhead, it's at least a familiar model.
I can also see the flip side, though, of letting autolink run, and then being able to always edit /that/ text without being forever frustrated by some rule that didn't consider your use case. Needs a ton of design to figure this out: no obvious next steps here for me.
Issue: When editing a post that has been modified by autolink, the user may need to do additional work to fix an error because of the modifications.
Request: A customer has requested the ability to see the "original unmodified" message before autolink touched it. Then when the edits are made, the autolink rules are re-applied on save.
From Customer: