Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>

[[ 🗃 ^yEzqv rel4tion-wiki ]] :: [📥 Inbox] [📤 Outbox] [🐤 Followers] [🤝 Collaborators] [🛠 Commits]

Clone

HTTPS: git clone https://vervis.peers.community/repos/yEzqv

SSH: git clone USERNAME@vervis.peers.community:yEzqv

Branches

Tags

master :: projects / tosaf / tickets /

1.mdwn

[[!tag /tickets/class/idea]]

[[!meta title=“Arbitrary predicate as path policy and update chooser”]]

Currently, hard-coded functions examine the file system and determine which plugin changes, if any, need to be made. The decision where to look and what to do with the findings is mostly hard-coded with very little configuration.

Perhaps adding support for using user-provided predicates instead of the hard-coded default can make Tosaf work for more use cases. This raises the question: How useful is the default algorithm, and how common is it to need something else, for which user-supplied functions are the best solution?

[See repo JSON]