Next Gen Ignores: Requirements

This issue replaces the ones that relate to fundamental issues with how our ignores work. The following is the up to date list of requirements: ### Certain Requirements - Must be understandable by someone who understands the interface in use by DropBox, OneDrive, etc. - Must be a simple tree view with checkboxes - Root of tree (=folder root) checked by default - Can uncheck root and then check just the branches that we want synced - Must be able to black list extensions - Must live in config (not .stignore files) - Must "live update". That is, if I ignore a file that was going to be pulled, we should not pull it. If I unignore a file that we are missing, it should be pulled shortly thereafter. - Must be able to specify if ignored files should be preserved or removed on directory delete. - Per what though? File extension? Directory? - Power user access to flexible, underlying patterns - Be able to to remove files for folders that are not picked, as it remove things that are now ignored. - Have inclusion and exclusion mode, ignore everything, include X, versus include everything, ignore X. ### Maybe? - Per directory file extension black lists ("never sync `*.tmp`") - Per directory file extension white lists ("only sync `*.doc`") - Should sync between devices - Ability to ignore a directory by the presence of a special file in it (`cachedir.tag`). Comments and discussion below. A project maintainer will keep the list above in sync as the requirements change or are cla

Posted by calmh on Nov 19, 2015, 1:59 PM

Tags

• github (Other)

Related issues

• struct's lifetime requirements can be bypassed via covariant field assignment
• Proposal to Reorganize the Moderation Team and Review Moderation Policies
• Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
• proposal: container/...: generic collection types
• Better Custom Endpoint BYOK
• A concrete policy for backward compatibility until Godot 5.0