Currently, to "update" a parser, tree-sitter manager removes and reinstalls it. Ideally, I think we'd want to keep the current revision id for each parser. This allows us to show an icon or notification if the parser needs an update, notify the user if a parser is up-to-date, or even add auto-update options (either via autocommands or a setup toggle). It's also something that was already available in nvim-treesitter, so we can look at their implementation for reference.
If we want to keep the ability to reinstall a parser, we could theoretically make a "repair" or "reinstall" function. This would be a little unnecessary imo, since the user could just remove and install themselves- but it is an option.
P.S. aware this is a large ask. I think the project should probably undergo that refactor first, and it might need to be split into several PRs, but I think it's worth it.
Currently, to "update" a parser, tree-sitter manager removes and reinstalls it. Ideally, I think we'd want to keep the current revision id for each parser. This allows us to show an icon or notification if the parser needs an update, notify the user if a parser is up-to-date, or even add auto-update options (either via autocommands or a setup toggle). It's also something that was already available in nvim-treesitter, so we can look at their implementation for reference.
If we want to keep the ability to reinstall a parser, we could theoretically make a "repair" or "reinstall" function. This would be a little unnecessary imo, since the user could just remove and install themselves- but it is an option.
P.S. aware this is a large ask. I think the project should probably undergo that refactor first, and it might need to be split into several PRs, but I think it's worth it.