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
Allow users to import/export both official and user-generated templates. JSON is probably the safest option but investigation is required as to whether or not Chrome allows file uploads or if copy-paste system should be used. Regardless, the system must allow multiple templates to be imported/exported at one time. Also, it is vital that the system is future-proof and is probably wise to include the extension version from the beginning should it be required further down the line.
When importing care should be taken to ensure name conflicts are resolved if/when they occur, always favoring the existing template. This could be done by attempting to append a number (starting from 1) to the name until an available alternative is found. The availability check should include any templates added previously in the import job in case the JSON includes duplicate templates.
Full validation should be carried out on the imported templates once completed. Imports should not be persisted automatically and should only be if/when the user clicks the "Save & Close" button.
The text was updated successfully, but these errors were encountered:
This has now been implemented and I'm happy with it so far. I'm sure any/all bugs will be picked up by users with normal use. May test offline Save As... functionality is triggered as expected (when there's no internet connection) so really just need to test window.navigator.onLine === false when offline.
Allow users to import/export both official and user-generated templates. JSON is probably the safest option but investigation is required as to whether or not Chrome allows file uploads or if copy-paste system should be used. Regardless, the system must allow multiple templates to be imported/exported at one time. Also, it is vital that the system is future-proof and is probably wise to include the extension version from the beginning should it be required further down the line.
When importing care should be taken to ensure name conflicts are resolved if/when they occur, always favoring the existing template. This could be done by attempting to append a number (starting from
1
) to the name until an available alternative is found. The availability check should include any templates added previously in the import job in case the JSON includes duplicate templates.Full validation should be carried out on the imported templates once completed. Imports should not be persisted automatically and should only be if/when the user clicks the "Save & Close" button.
The text was updated successfully, but these errors were encountered: