-
Notifications
You must be signed in to change notification settings - Fork 24
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
Aliases #184
Comments
related NLog/NLog#4716 |
1. What do you think about this design?
Think it is nice with tags/keywords, just like one have for normal nuget-packages.
But still think the actual alias-symbol-names should primarily be documented on the individual wiki-pages.
Btw. Could my pull-request #183 about cleaning up platforms be merged first?
|
Nothing has been removed with NLog 5, so the wiki-pages remains the same. There might be a new nuget-package, but I think people will recognize from the NLog-version-number whether it is relevant for NLog4 or NLog5. For me it is okay to only maintain a single NLog-config-page (since it matches the wiki-pages). |
Im afraid that people get confused with the changes between nlog 4 and 5. We need at least someting to the docs for that. And im thinking of adding a note to https://nlog-project.org/config/ I consider this as a showstopper :( |
The aliases are new for nlog 5. But im aware of the large user base of nlog 4 |
That is usually how the wiki-pages works. When adding details about new features, then one also specify what version of NLog is required. |
Since the alias-feature seems to be very difficult to explain and understand, and it is blocking the NLog 5.0 release (Cannot get my pull-requests merged for NLog5-docs), then I'm fine with either option:
|
I just added |
@snakefoot I think it's important to make the aliases visible and searchable on https://nlog-project.org/config.
The text was updated successfully, but these errors were encountered: