Skip to content

Christian Nüssgens

My feedback

3 results found

  1. 8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Christian Nüssgens supported this idea  · 
  2. 183 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Christian Nüssgens supported this idea  · 
  3. 5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Christian Nüssgens supported this idea  · 
    An error occurred while saving the comment
    Christian Nüssgens commented  · 

    Yeah, full ack! I'm missing this feature, too.

    I wanted to implement a quick-poll slash handler where one could display which user voted for each option. In order to achive something like that my "dump" slash-command-handler would need an web-api connection, which would require additional - and imho unnecessary - configuration-overhead.
    I just need _some_ display-name so that useres can distinguish each other.

    It would be very nice to have the `user_name`-string included in the JSON POST-content (in addition to `context`-object and `user_id`-string) whenever any user presses one interative button.

    Just like `user_name` and `user_id` are included in the headers of the initial slash-command request

Feedback and Knowledge Base