Some kind of version history for lists would be nice.
This would be kinda similar to the use-case for the planned projects feature, but list specific, instead of needing to upload multiple lists to a project.
Ways to implement this could be:
-
A version history table that is just a pivot table between the load_order and files tables.
-
Move the version field to load_order_files pivot table, and simply return the newest entry on normal GET, then expose a ?version= filter to get by version.
One limitation to the above, is that it would only track version number and the files associated with that version, it wouldn't track the description. This could be resolved by potentially having the load_orders table only include user_id and slug columns, then the pivot table between load_orders and files has version/desc/website/files/etc. This would be more complicated since it would require editing almost 3000 lists in the database.
Some kind of version history for lists would be nice.
This would be kinda similar to the use-case for the planned projects feature, but list specific, instead of needing to upload multiple lists to a project.
Ways to implement this could be:
A version history table that is just a pivot table between the load_order and files tables.
Move the version field to
load_order_filespivot table, and simply return the newest entry on normalGET, then expose a ?version= filter to get by version.One limitation to the above, is that it would only track version number and the files associated with that version, it wouldn't track the description. This could be resolved by potentially having the
load_orderstable only includeuser_idandslugcolumns, then the pivot table betweenload_ordersandfileshas version/desc/website/files/etc. This would be more complicated since it would require editing almost 3000 lists in the database.