You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 601ccfc
Browse filesBrowse the repository at this point in the historyBrowse files
feat: move several models in one sqb mv and match carried declaration layouts (#1206)
* fix: give a carried declaration the shape of its destination role
When sqb mv carries a scoped declaration to a wider owner, the file now
matches the layout of the role folder it lands in instead of always being
written directly in it. An empty role keeps the source's group folder, a
grouped role keeps the source's group, and a direct role drops it. A file
without a group that must join a grouped role is refused with a message to
move it into a group first, rather than writing a layout that verification
rejects for mixing direct and grouped files.
Placement relocation now accepts several resource moves at once.
* feat: move several models in one verified sqb mv
sqb mv now takes several TARGET DESTINATION pairs, or --from-file with one
pair per line (tab or space separated, # comments and blank lines allowed).
The project compiles once before planning and the edited project once
after. Every move is planned together: declarations and unit tests are
placed for the state after all moves, a model may take a file or name
another move leaves, and a batch that moves a model twice, sends two models
to one file or gives them one name is refused. Nothing is written unless
the whole batch verifies; --dry-run prints the combined plan, and JSON
output lists the moves. A single move plans and prints as before.
* fix: refuse a move that sends two declaration files to one path
Two carried declaration files could share one target, either from two moved models' same-named local files or from grouped files flattened into a direct role. Planning now refuses this up front, naming both files, instead of leaving it to a confusing verification compile error.
0 commit comments