Closed Nikolai2038 closed 9 months ago
I want to keep the plugin more simple as there are already many settings. So I won't add this setting. I don't think many people encounter that file limt. What are you doing that you encounter this? You should still be able to commit and push via the command palette.
Yeah, that's why I use external VCS to work with GIT instead of Obsidian Git. You are right - I can still commit and push via this plugin, but I don't quite understand, why you need to limit it's functionality and don't provide the way to customize it.
Quite sad, but it is your choice.
If I remember correctly it was for performance reasons. The view became unresponsive with too many files listed. There may be a better way to solve this, but that was the easiest one at that point.
Hi!
I was working with Obsidian Git in big repository with a lot of notes. Got
Too many changes to display
error too often and was forced to use external VCS tool. Then I looked at the source code of this plugin and find out, that the limit is500
and there is no setting to change that. So I add new settingmaximumNumberOfFilesToDisplay
with default value500
. Hope I did it right!Also, I noticed that when the value of this new setting is reduced to the error
Too many files changes
(whenrefresh()
is called), then an error in consoleUncaught (in promise) TypeError: Cannot read properties of null (reading 'firstElementChild')
occurs:So I add
if (!btn) { return; }
for that torefresh()
method insourceControl.svelte
.