The Graph extract crate does not create imports when the type is custom but not a direct ref
Categories
(MailNews Core :: Networking: Exchange, defect)
Tracking
(Not tracked)
People
(Reporter: babolivier, Assigned: babolivier)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files, 1 obsolete file)
| Assignee | ||
Comment 1•1 month ago
|
||
Which it turns out is essentially what D279798 was proposing initially (in a
slightly different way).
I'm also including the ItemBody type as an example (since that's a type that
didn't get properly imported before this change).
| Assignee | ||
Updated•1 month ago
|
Pushed by edicharry@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/bcee52fba79c
Create imports for custom Graph types even it they're not a direct ref. r=jtracey
Comment 3•1 month ago
|
||
Updated•1 month ago
|
Comment 4•1 month ago
|
||
We picked up a rust formatting error from this one: https://treeherder.mozilla.org/jobs?repo=comm-central&revision=bcee52fba79c511a4ee3ea531997c30182a8edc4&selectedTaskRun=Jpp0GvBNSRCxatANw197aA.0
Brendan - can you submit a follow-up patch to correct the formatting? I tried doing it myself, but it wound up changing generated code, so I think we need to update the code generator for the new formatting rules we got with Rust 2024 and regenerate.
Comment 5•1 month ago
|
||
Nevermind - I read the README and realized the generated code just needs to be formatted like normal, so I submitted a follow-up patch for that.
Comment 6•1 month ago
|
||
Updated•1 month ago
|
Updated•1 month ago
|
Pushed by vineet@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/310dc8aa5f1f
follow-up: Fix formatting for updated Rust edition. r=jtracey
| Assignee | ||
Comment 8•1 month ago
|
||
Bah, sorry about that 🙁
Thanks for fixing!
Description
•