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
I’d like to discuss a possible improvement to folder default languages.
I use massCode with a cloud-synced local vault and automated local AI workflows. Snippets come from different sources, so some end up with an incorrect language or Plain Text.
Currently, a folder’s default language is applied only when creating new snippets in that folder. Existing snippets and nested folders keep their current language settings. This is manageable for a few entries, but becomes tedious when correcting many imported or generated snippets.
I initially expected the folder setting to propagate to its contents, but learned that it intentionally applies only to new snippets.
I implemented a possible opt-in bulk-update flow:
When changing a folder’s default language, show a dialog if the folder contains nested folders or snippets.
Optionally update the default language of all nested folders.
Optionally update the language of all snippets in the selected folder and its descendants.
The selected folder’s own default language is always updated; propagation remains explicitly optional.
I find this useful for bulk correction and would appreciate feedback on whether this behavior would be appropriate for the main branch.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I’d like to discuss a possible improvement to folder default languages.
I use massCode with a cloud-synced local vault and automated local AI workflows. Snippets come from different sources, so some end up with an incorrect language or Plain Text.
Currently, a folder’s default language is applied only when creating new snippets in that folder. Existing snippets and nested folders keep their current language settings. This is manageable for a few entries, but becomes tedious when correcting many imported or generated snippets.
I initially expected the folder setting to propagate to its contents, but learned that it intentionally applies only to new snippets.
I implemented a possible opt-in bulk-update flow:
The selected folder’s own default language is always updated; propagation remains explicitly optional.
I find this useful for bulk correction and would appreciate feedback on whether this behavior would be appropriate for the main branch.
All reactions