Skip to content
This repository was archived by the owner on Dec 13, 2018. It is now read-only.

[Discussion] Logging API change #350

Closed
BrennanConroy opened this issue Jan 28, 2016 · 3 comments
Closed

[Discussion] Logging API change #350

BrennanConroy opened this issue Jan 28, 2016 · 3 comments
Milestone

Comments

@BrennanConroy
Copy link
Member

Changes from #331 see announcement aspnet/Announcements#148

@cwe1ss
Copy link
Contributor

cwe1ss commented Feb 15, 2016

The Log... functions are now in 3 flavors

Log....(this ILogger logger, EventId eventId, Exception exception, string message, params object[] args);
Log....(this ILogger logger, EventId eventId, string message, params object[] args);
Log....(this ILogger logger, string message, params object[] args);

Wouldn't it be good to also have Log....(this ILogger logger, Exception exception, string message, params object[] args); to support writing Exceptions without an EventId? As far as I understood, those EventIds are optional, right?

@tuespetre
Copy link

While I can understand the move from ILogValues to IReadOnlyList<KeyValuePair<string,object>>, I feel that the overloads should have been left in place. params object[] can feel very hokey and I would much prefer to define explicit classes that implement IReadOnlyList<KeyValuePair<string,object>> to represent the state of logged events.

@muratg
Copy link

muratg commented May 12, 2017

We are closing this issue because this was just an announcement issue. If you still have any issues or questions, please log a new issue with any additional details that you have.

@muratg muratg closed this as completed May 12, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants