Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

namespace System.Net
{
    [Serializable]
    [...]
    
    public class CookieException : FormatException, ISerializable
    {
        public CookieException() : base()
        {
        }

        // Please make this public
        public CookieException(string? message) : base(message)
        {
        }

throw new CookieException("🥮");
throw new CookieException("🍥");
throw new CookieException("🍪");
throw new CookieException("🍩");
throw new CookieException("🍰");

Personally I would be fine with this, and it looks like a trivial addition. Most BCL exception constructors allow passing a message string, it's CookieException that seems to be exceptional in this sense.

@dotnet/ncl any objections against marking this ready for review?

Triage: assigned to Future given it's not critical. Once the API is approved, we can mark it help wanted, since it's a good candidate for community contribution.

Video

• We should also add the one that takes inner exceptions, for consistency with other exceptions

namespace System.Net;

public partial class CookieException
{
    // Existing ctors:
    // public CookieException();
    // public CookieException(SerializationInfo, StreamingContext);
    public CookieException(string? message);
    public CookieException(string? message, Exception? innerException);
 }

@terrajobst Incredible! Attached video - transparency level 1000.
I am impressed. Really.

@mateusz-dobrowolny

Glad you like it! You can find an aggregate of all our notes here, in case you're ever curious why a given API ended up like it did. I also link notes from API Catalog, for example here.

@terrajobst @vcsjones Can I implement the feature? Happy to assign me.