-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Page/RichText Footnote Validation #17
Comments
One way around it is to keep track of the references on the page and probably drop on paste. |
Reusing footnotes across multiple pages is something that has crossed my mind a few times, but I feel like this could get out of control quite quickly depending on the number of footnotes a website has. Things that would need to be REALLY good would be:
|
It's too complex to reuse Footnotes IMHO. We run into a complex issue where if the footnote is edited on one page, the consequences on another page reusing the same footnote are undefined and need to be resolved by the user through additional UI. |
Draftail allows copying and pasting of text from one instance to another.
If I copy text containing a footnote reference from one page to another, there won't be a footnote related to that page to display.
Current Behaviour:
The page saves fine and renders with no errors. However, there is an unlinked footnote reference in the page as there isn't a related footnote to link to.
Expected Behaviour:
On save, a validation error is raised that informs the user that there is an invalid footnote in the RichText.
Current thoughts on how to fix:
I think this is going to need a Mixin that people can add to their Page models. The mixin will define the validation logic for the footnotes.
The text was updated successfully, but these errors were encountered: