hakowork/rojo
3
0
Fork 0
mirror of https://github.com/rojo-rbx/rojo.git synced 2026-10-22 21:41:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update submodule and enhance syncback confirmation dialog

Browse source 
- Updated the `vscode-rojo` submodule to the latest commit.
- Modified the syncback confirmation dialog title to indicate its beta status and adjusted its dimensions for better usability.
- Enhanced the warning message to clarify the differences between live syncback and CLI syncback, helping users make informed decisions.

These changes aim to improve user experience and provide clearer guidance during the syncback process.
This commit is contained in:
Joe 2026-02-19 05:16:40 -06:00
parent 8d17b1de1f
commit 57112a9f22
3 changed files with 17 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

14
.cursor/commands/format.md
View file

@ -16,8 +16,18 @@ Run formatting and static analysis (linting) across the entire project.
bash scripts/format.sh
```
**Monitor the script output as it runs.** If a step fails, investigate the failure and fix it manually before re-running.
**Monitor the script output as it runs.**
### 2. Report
### 2. Fix ALL Failures
If any step fails, you MUST fix the issues and re-run until everything passes. This applies to **every** failure -- Clippy, Selene, Prettier, all of them.
**Clippy is not optional.** Fix every Clippy warning, even if the warning is in code you did not write or that existed before your changes. There is no "pre-existing" or "before my time" exception. If Clippy reports it, fix it. The CI gate runs `cargo clippy` and will reject the PR regardless of who introduced the warning.
The same rule applies to Selene warnings on Lua code. If the linter flags it, fix it.
Keep re-running the format script until the overall result is **PASS** with zero failures.
### 3. Report
Once formatting passes clean, provide a brief summary and confirm the final result.