XAML code-behind bridges have no candidates after C# is owned by its first-party package #430
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index#430
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A1X e3 and TimeLine16.0 on core 0.41.14
ea08d164report tier_bridge=0. Also observed on 0.41.13. Both XAML source bridges are approved in de.h-dv.xaml 0.3.0: paired_file type->csharp class (last_segment), call->csharp method (identity), bridge_source granted. C# is de.h-dv.csharp 0.1.6.Repro shape: xDSetArgsWindow.xaml:77 Click="bOk_Click"; paired xDSetArgsWindow.xaml.cs:52 private void bOk_Click(object sender,RoutedEventArgs e), unique in its paired file. x:Class is TimeLine.Client.Framework.xDSetArgsWindow; same namespace and partial code-behind class. find_references returns zero. e3 corroborates 526 call refs/0 resolved and 394 type refs/0 resolved.
Source triage: fill_bridge_cands correctly requires bridge_destination on the destination contribution. Builtin components held it, but the first-party C# manifest requests seven resolver capabilities without bridge_destination. This is a likely package migration gap; isolated signed-package reproduction is still required. Preserve this two-sided permission check: request destination authority in a new C# package version and only use an explicit operator grant. Test withholding either side, paired-file decoys, ambiguous candidates and binding paths without DataContext evidence. Do not widen bridge scope or infer receivers by bare names. #154 tracks broader containment/framework limitations and is not an exact duplicate.
Shipped in core 0.41.15 and C# 0.1.7. All four platform archives were independently checked against the signed catalog and contain the byte-identical official signed C# 0.1.7 package. The actual official 0.41.14→0.41.15 existing-database upgrade reproduced null class/handler targets before the upgrade and resolved the paired class/private handler afterwards, with unrelated-file and binding decoys still excluded. No database deletion; inode preserved. Both grants, source declarations, paired-file scope and uniqueness remain enforced. Upgrade core first: C# 0.1.7 requires >=0.41.15; grant requested package capabilities explicitly. Final release CI passed.
Independent e3 production-project confirmation on published core0.41.15(065c8864), C#0.1.7(38194755) + XAML0.3.1(0c65e958), keeping the existing DB: after the normal approval-triggered rebuild completed, XAML calls resolved503/526(95.6%, previously0), types392/394(99.5%, previously0), parse_errors0. The reported private C# handler's find_references now includes the actual XAML call with resolved_by=bridge. Only the two pre-existing template XAML fixtures remain partial. Read/member_access rates are separate unsupported cases and are not claimed fixed. A subsequent idle-timeout daemon restart explains a fresh reconciling disclosure, not loss of the measured bridge result.