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
{{ message }}
This repository was archived by the owner on Jan 13, 2025. It is now read-only.
Description:
Currently, users must create files while adhering to strict JSON naming conventions, including avoiding spaces and ensuring the file ends with a .json extension. The following changes are proposed:
Title Display in Explorer: Display the document title in the file explorer for better visibility.
Automatic Filename Formatting:
Replace spaces in user-provided names with hyphens (-).
Ensure the JSON file name matches the document title.
Automatically append .json to the filename if not already included.
Backend Validation: Implement a check that adds the .json extension only if the user has not included it.
Expected Outcome:
This will streamline file creation, reduce user errors, and improve overall usability.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description:
Currently, users must create files while adhering to strict JSON naming conventions, including avoiding spaces and ensuring the file ends with a
.json
extension. The following changes are proposed:-
)..json
to the filename if not already included..json
extension only if the user has not included it.Expected Outcome:
This will streamline file creation, reduce user errors, and improve overall usability.
The text was updated successfully, but these errors were encountered: