Skip to content

Switching git branches should not rapidly trigger multiple file changes, but only trigger each changed part once #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
hawkerboy7 opened this issue Oct 30, 2022 · 1 comment
Closed

Switching git branches should not rapidly trigger multiple file changes, but only trigger each changed part once #34

hawkerboy7 opened this issue Oct 30, 2022 · 1 comment
Labels
high prio

Comments

@hawkerboy7
Copy link
Owner

Switching git branches should cause the file watcher to see the changes but not act upon them for +-0.4s seconds or so.

Perhaps always add a change delay of +-0.4s which makes it wait until there are no changes for that duration and then trigger each of the changed parts once instead of "for-every-change". This should auto-include the git branch change issue.
@hawkerboy7
Copy link
Owner Author

Resolved in 2dfc7e2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
high prio
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hawkerboy7