Skip to content
This repository was archived by the owner on Sep 21, 2026. It is now read-only.
This repository was archived by the owner on Sep 21, 2026. It is now read-only.

Server Side Notifications with referenceID? #122

Description

@razblack

Hello,

I have been using growl 2 and it is wonderful; however, I have a case where it would be nice to be able to control the referenceId from server side notifications.

In order for me to do this, I had to modify growl 2 (angular-growl.js line#275) and add a simple assignment such as:

config.referenceId = message['referenceId'];

It's a bit hacky, but seems to work.

In ASP.NET MVC, my model looks such as:

public class GrowlMessages
{
    public List<GrowlMessage> growlmessages;
    public GrowlMessages()
    {
        growlmessages = new List<GrowlMessage>();
    }
}

public class GrowlMessage
{
    public string growltext { get; set; }
    public string growlseverity { get; set; }
    public string growltitle { get; set; }
    public int referenceId { get; set; }

    public GrowlMessage()
    {
        referenceId = 0;
    }
}

and my app.js sets it up as:

    growlProvider.messagesKey("growlmessages");
    growlProvider.messageTextKey("growltext");
    growlProvider.messageSeverityKey("growlseverity");
    growlProvider.messageTitleKey("growltitle");

Would be great to be able to define a growlProvider.messageId in the app to integrate better with your schema.

maybe this is a feature request? :D

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions