bleedingdeacons / link / 33967381417
92%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 11
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 95.17%. Remained the same
33967381417

push

github

web-flow 
feat: publish a GitHub Release with an APK built at the version it names

* chore: compile the XAML bindings, stamp the assemblies, cover the seams

Four build-quality gaps against Hand, none of them behaviour changes.

MauiEnableXamlCBindingWithSourceCompilation was missing, so every
{Binding ... Source=...} fell back to reflection — App.xaml,
ComposePage.xaml and MessagesPage.xaml all set Source, so this was real
rather than hypothetical. Reflection is slower everywhere and unsafe
under the full trimming an iOS Release build uses: the member it
reflects over can be trimmed away, and the binding then resolves to
nothing on a device with nothing wrong at compile time. This matters
more here than in Hand, because this repo has an iOS head.

XC0022-XC0025 and XC0045 are now errors. They are what the XAML compiler
raises when it cannot compile a binding and is falling back; as warnings
they scroll past in a build that says "succeeded".

AssemblyVersion and FileVersion were at the SDK default of 1.0.0.0 while
the app displayed 1.4.0. Same drift Hand hit, where the Windows head
stamped the wrong version onto every log event. Derived from
ApplicationDisplayVersion, which bump-version.sh already rewrites, so
they follow a release without the script needing to know they exist.
InformationalVersion additionally carries a UTC build timestamp.

.github/dependabot.yml — actions here are pinned to commit SHAs, which
is safe against a tag being repointed but means a pin never picks up an
upstream fix on its own. Nothing was rewriting them. The nuget half also
gives the NU1608 constraint warnings in the Android graph a way of
getting better rather than worse.

Tests for the two seams the branch coverage said were thin.

The JSON coercion helpers had one branch at 0%: numbers arriving as
strings. Fellowship reads its rows through wpdb, which returns every
column as a PHP string, so "id":"9" is what an uncast route sends — the
fallback existed and nothing would have n... (continued)

729 of 766 relevant lines covered (95.17%)

11.27 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33967381417.1 11
95.17
GitHub Action Run
Source Files on build 33967381417