Eilon Lipton

This is... very interesting! I haven't played with source generators but they certainly open up some incredible solutions. Here are my thoughts on this: 1. So long as it isn't...

I'll take a look at this! I'm not super familiar with Blazor's edit experience (I've only tried a few samples/tutorials) so I'll play with what you have and keep this...

OK looks like I can call: ```c# Issue.Labels.AddToIssue(......); ``` To more easily do what I want. But the issue above still seems valid.

Note: Looks like Issue.Labels.AddToIssue() doesn't work due to an Octokit bug (https://github.com/octokit/octokit.net/issues/1928), and also due to a GitHub issue anyway.

Here's the code I have to do to work around this issue: ```c# var issue = await gitHub.Issue.Get("owner", "repo", issueNumber); var issueUpdate = new IssueUpdate { Milestone = issue.Milestone?.Number //...

BTW I don't see the problem with Assignee: I tested it out by only setting milestone and labels, and the existing assignee(s) on the issue remained.

Yeah I kept wondering why things like Comment count were always 0 for PRs. Kind of frustrating that I have to make additional calls for each PR I'm interested in......

@egil that could be quite reasonable. Can you send a PR to Mobile Blazor Bindings to propose those changes? I tried to find the right balance for the design of...

Sounds good, I look forward to seeing what changes we should make!

@congzhangzh - Blazor syntax and files are adaptable to almost any UI system. We have an experimental project where it was adapted to render native Xamarin.Forms controls here: https://github.com/dotnet/MobileBlazorBindings/ Maybe...