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
gui: say where the files go, and let a declaration describe itself
Three fixes, all of them from the owner looking at the screen rather than from
a guard. That step has now found something every time it has been taken.
The output directory is written out in full instead of as a dot, with a Choose
button beside it. A dot is clear in a terminal, where you walked into the
directory yourself. Started from a desktop it means somewhere, and this is the
one part of the tool that writes into other people's directories. The box stays
a box, so a path somebody sent you can still be pasted in.
A text setting can say what sort of text it takes. "text" under a field is a
word where a description should be, and the declaration for the spread of a
boundary set already knew it wanted a list of sizes with nowhere to put it. The
guard for that found two more the same way, in zip and targz.
What a preset typically finds is a list of lines. Run together it read as three
times as many findings as there are, because the entries have commas in them.
The picker cost one module and which one is the point. fyne.io/fyne/v2/dialog
imports github.com/FyshOS/fancyfs, which was already named in our module graph
because the toolkit requires it - importing dialog moved it from named to
downloaded, checksummed and compiled in. Checked before accepting: BSD-3, one
way compatible with GPL-3.0 like the eleven other BSD-3 modules here, 129 lines,
written by the author of the toolkit itself, and reached from a single line
where it decorates folder icons. Tidying afterwards pruned kr/text, which took
creack/pty out of the graph, so the dependency gate went from 69 modules to 68
and its expected list was changed deliberately rather than to make it pass.
That import also showed a hole in the notices guard. It asked whether every
listed module is still built and never the other way round, so a module that
ARRIVED went unlisted - which is the direction the licences care about, since
they require the notice to travel with the code that ships. It asks both now.
Its first run raised two false alarms worth recording: goccy/go-yaml and x/text
are noticed under their own headings with the whole licence text rather than as
table rows, which is a stronger notice and not a weaker one.
Host gained ChooseDirectory and it always calls back, including with nothing
when somebody cancels. A host that stays silent on cancel leaves the caller's
handling of that answer unreachable from any test, which is how the mutation for
it first came back NOT CAUGHT.
Guards 247 to 252, mutations 229 to 235.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments