You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Redirect rules are both project level and version level, so they are not a great fit for our configuration file, and our redirect UI is not the best solution for this either.
One way that we could overcome some of the issues with our redirect UI, and still allow for easier editing of these redirects, would be an import/export function. This would export to json/yaml/csv/something and would expect a similar input format on file upload.
Pieces:
Form changes to allow file upload on redirects listing page
Validation of input format, validating redirect types/etc
Do we wipe out all existing redirects on import? Overwrite? Can we easily detect and overwrite? Allow an option for "Overwrite all rules" on import?
Obviously there is overlap with the API function here as well, but import/export is a much more user friendly way of making the bulk changes if users aren't familiar with using the API.
Alternatively, we could also make this a separate command/etc, which would just be a wrapper around the API interactions:
% readthedocs-redirects import foo.json
The text was updated successfully, but these errors were encountered:
There are a couple of tools out there that make use of our API to keep redirects in sync, maybe we can have an official tool, or just let the community do it.
Redirect rules are both project level and version level, so they are not a great fit for our configuration file, and our redirect UI is not the best solution for this either.
One way that we could overcome some of the issues with our redirect UI, and still allow for easier editing of these redirects, would be an import/export function. This would export to json/yaml/csv/something and would expect a similar input format on file upload.
Pieces:
Obviously there is overlap with the API function here as well, but import/export is a much more user friendly way of making the bulk changes if users aren't familiar with using the API.
Alternatively, we could also make this a separate command/etc, which would just be a wrapper around the API interactions:
% readthedocs-redirects import foo.json
The text was updated successfully, but these errors were encountered: