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

Suggestion: Make SymbolRenamer and other internal APIs publicly accessible #1156

Closed
naturecodevoid opened this issue Aug 14, 2023 · 2 comments · Fixed by #1161
Closed

Suggestion: Make SymbolRenamer and other internal APIs publicly accessible #1156

naturecodevoid opened this issue Aug 14, 2023 · 2 comments · Fixed by #1161

Comments

@naturecodevoid
Copy link

Hi, I'd like to be able to use Roslynator's SymbolRenamer class without a hacky solution like going through the CLI.

I'm sure there are a lot of other internal APIs that would be beneficial to API users.

Do you think this would be possible?

@josefpihrt
Copy link
Collaborator

Hi,

I think it's good idea to make SymbolRenamer public. Please see the PR for the details.

Regarding the other API: currently there is no template for it but it's necessary to create an issue for each logical group of API and to describe the API in a way similar what is here.

@naturecodevoid
Copy link
Author

Thank you so much! Sorry I didn't get around to the unit tests.

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

Successfully merging a pull request may close this issue.

2 participants