hakowork/rojo
3
0
Fork 0
mirror of https://github.com/rojo-rbx/rojo.git synced 2026-10-23 05:51:39 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Optimize syncback process and enhance patch selection logic

Browse source 
- Improved the syncback functionality by detecting unchanged output file hashes to avoid unnecessary writes, optimizing performance for larger projects.
- Updated the patch selection logic to ensure that auto-selection only occurs when the current selection matches the default, enhancing user experience during patch reviews.

These changes aim to streamline file synchronization and improve the clarity of patch management in the application.
This commit is contained in:
Joe 2026-03-01 06:43:25 -06:00
parent a15f4f1aa8
commit 63b0b031ff
2 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

12
TODO.txt
View file

@ -333,20 +333,16 @@ when you commit changes on git, it's considered unchanged. we should send like t
there is some process that is making disconnecting after a one-shot sync completes take FOREVER if the server is yielding (usually from the reconciler)
- once the one-shot sync completes, it should not be waiting for additional things to come from the server. it just needs to kill the connection immediately. and go back to the main page.
[init scripts]
scripts actually named init or probably even Init cause the sync engine to completely break. it will syncback, but then i cannot even serve the project.
this needs to be slugified when the name exactly matches init, ignoring case [for anything, not just scripts!]
[one shot mode change]
new changes that come in / out during the review menu on the plugin is really disorienting.
we should just make it stop accepting new changes once it has the full patch ready and displayed to the user
any further changes should have to be done NEXT one-shot sync
[syncback]
detect when the output file hash is the same, and dont write to it
[sync]
for the automated git staging we do on sync, manually selection Studio should NOT automatically stage changes!
detect when the output file hash is the same, and dont write to it.
because have already loaded it, we can detect this.
this is an optimization to avoid writing 100,000 files or something on larger projects when file bytes match perfectly, or directories verifiably already exist.
make sure this is applied to plugin-based syncback, too.
[auto select studio/atlas]
when things get added AFTER the fact because we send the git history hashes on connect rather than continiously, it auto-selects Studio for things that are being edited in real-time in the sync dialog