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
{{ message }}
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
[Proposal] New Assembly/Package Title format #3897
Thanks @Nirmal4G for this proposal, makes sense. I was just confused at first, as I thought you were suggesting changing package ids, but it's just making our existing titles a bit more consistent, which sounds great!
I'm just getting back into things, so let's noodle on the names a bit this week in case we have any suggestions. Thanks again!
Thanks @azchohfi, yeah we couldn't use the term 'Basic' here. Let's just label it with the technology for now.
What's the reason? If it's too vague or generic, we can use Common/Core, etc.. But that's just introducing different words for the same meaning into what is seemingly a simple package title.
If we are worried about discoverability (Web/NuGet search), package tags will take care of it. Package titles should be simple yet descriptive but brief.
@Nirmal4G "Basic" isn't any more descriptive and also is more diminutive. It's also introducing another term we're not using to describe any of the packages anywhere else. We can think about if there's a better term for the future, but for now let's just keep it simple and work on merging the PR as there's already been a lot of discussion on things that have very minimal impact overall. Like the Title doesn't really show up anywhere in VS or Nuget.org.
That's what I updated them too. We can fiddle on this later if we need to, but think the updated formatting with the hyphen is fine. I've committed my suggestions, so all that's left on that PR is the open comment about reverting the targetframework for Uno. If you can do that bit, we can get that PR merged and move on to your other PRs.
Activity
[-]Update package titles and consolidate build logic[/-][+]Update package titles and refactor markdown files[/+][-]Update package titles and refactor markdown files[/-][+][Proposal] New Package title format[/+][-][Proposal] New Package title format[/-][+][Proposal] New Assembly/Package title format[/+][-][Proposal] New Assembly/Package title format[/-][+][Proposal] New Assembly/Package Title format[/+]Kyaa-dost commentedon Mar 29, 2021
Thanks @Nirmal4G for the proposal. Opened this up for discussion to get insight from the rest of the community as well.
michael-hawker commentedon Apr 22, 2021
Thanks @Nirmal4G for this proposal, makes sense. I was just confused at first, as I thought you were suggesting changing package ids, but it's just making our existing titles a bit more consistent, which sounds great!
I'm just getting back into things, so let's noodle on the names a bit this week in case we have any suggestions. Thanks again!
Nirmal4G commentedon Jul 14, 2021
@michael-hawker Review in PR
What's the reason? If it's too vague or generic, we can use
Common/Core, etc.. But that's just introducing different words for the same meaning into what is seemingly a simple package title.If we are worried about discoverability (Web/NuGet search), package tags will take care of it. Package titles should be simple yet descriptive but brief.
michael-hawker commentedon Jul 14, 2021
@Nirmal4G "Basic" isn't any more descriptive and also is more diminutive. It's also introducing another term we're not using to describe any of the packages anywhere else. We can think about if there's a better term for the future, but for now let's just keep it simple and work on merging the PR as there's already been a lot of discussion on things that have very minimal impact overall. Like the Title doesn't really show up anywhere in VS or Nuget.org.
Nirmal4G commentedon Jul 14, 2021
Some of the new titles you've proposed doesn't follow the format I mentioned above. If
Basicsdoesn't cut it, How about usingCommon/Core?Then, does it matter when there's a (new) term to describe those packages?
If we can't decide right now, I could separate the title changes into a new PR.
michael-hawker commentedon Jul 15, 2021
That's what I updated them too. We can fiddle on this later if we need to, but think the updated formatting with the hyphen is fine. I've committed my suggestions, so all that's left on that PR is the open comment about reverting the targetframework for Uno. If you can do that bit, we can get that PR merged and move on to your other PRs.