Proposal: usage-based manifest entries

[43081j]

While bouncing ideas around with a friend on this recently, I realised I think we need some kind of usage-based suggestions

For example:

import {foo} from 'target-package';

foo(); // we want to replace this with `replacement-1`

foo({ someFlag: true }); // replace this with `replacement-2`

in this situation:

• if all usages are foo() (i.e. no options passed), we want to suggest replacement-1
• if one or more usages have options passed, we want to suggest replacement-2

we can't currently achieve this through the manifests and would end up with such logic in consumers, like the lint plugin.

maybe we could have an ast-grep JSON rule in the manifest entry to define "if this rule matches, use this replacement"

i'm not sure yet but i feel like if we had this, we'd benefit massively and could add many more modules.

opinions very much welcome! would love to hear all your ideas on this