Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX: CS1574: XML comment has cref attribute 'Enum' that could not be resolved #72

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

OhFlowi
Copy link
Contributor

@OhFlowi OhFlowi commented Mar 19, 2024

BREAKING CHANGE: Changed the namespace of the generated extension methods to the same as the enum. Moved the generated attribute namespace to the generator namespace.

Fixes also "CS1574 XML comment has cref attribute 'Enum' that could not be resolved" bugs that have occurred since the last release.

The original #70 was closed with "duplicate #71", which is not nearly true.

…hods to the same as the enum. Moved the generated attribute namespace to the generator namespace.
@OhFlowi OhFlowi changed the title BREAKING CHANGE: Changed the namespace of the generated extension met… FIX: CS1574 Mar 19, 2024
@OhFlowi OhFlowi changed the title FIX: CS1574 FIX: CS1574: XML comment has cref attribute 'Enum' that could not be resolved Mar 19, 2024
/// <param name="namespaceSymbol">The namespace symbol.</param>
/// <param name="fullName">Optional. The initial full name to start with.</param>
/// <returns>The full name of the namespace.</returns>
public static string FullNamespace(this INamespaceSymbol namespaceSymbol, string fullName = null)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this method exist in to SymbolExtensions

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The original FullNamespace extension in the SymbolExtensions file is replaced by the new extension file. The why I already explained in the other comment.

/// <summary>
/// Provides extension methods for <see cref="INamespaceSymbol"/> objects.
/// </summary>
public static class NamespaceSymbolExtensions
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is better to have one extension, not several

Copy link
Contributor Author

@OhFlowi OhFlowi Mar 29, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it is better to have a single extension file for a single target, especially if you only have a few methods.

But since this new file targets INamespaceSymbol and not ISymbol like the already existing FullName extension, the new file has a reason to exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants