Skip to content
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

Correct docs for Send-GSChatMessage #256

Closed
scrthq opened this issue Jan 7, 2020 · 0 comments
Closed

Correct docs for Send-GSChatMessage #256

scrthq opened this issue Jan 7, 2020 · 0 comments
Assignees
Labels
documentation update Documentation update needed for this
Milestone

Comments

@scrthq
Copy link
Member

scrthq commented Jan 7, 2020

From Disqus on the docs page @ https://psgsuite.io/Function%20Help/Chat/Send-GSChatMessage/#__comments


Skylar Ragan • 40 minutes ago
Get-GSChatWebhook appears to no longer be a valid function in this module. It seems the key for the webhook value can now be named directly with the webhook parameter.

•Reply•Share ›
Avatar
Nate @ SCRT HQ Mod Skylar Ragan • 36 minutes ago
Hey Skylar Ragan - Any examples or links that show the change in usage? Definitely want to get those cleaned up if I can, but I'm not sure exactly what the alternative you are suggesting is so I have no way to validate that claim.

•Edit•Reply•Share ›
Avatar
Skylar Ragan • a minute ago
So both Example 1 as well as the description for the -Webhook parameter itself suggest getting the webhook URL via the Get-GSChatWebhook command; ie. -webhook (Get-GSChatWebhook RoomName). But when attempting to call Get-GSChatWebhook an error is thrown stating it's not recognized as the name of a cmdlet, function, script file, or operable program. Instead, both Example 2 and Example 3 seem to suggest calling the room name directly; ie. -Webhook RoomName, which I've been able to verify works in the most recent version of the module.

•Reply•Share ›

Avatar
Nate @ SCRT HQ Mod Skylar Ragan • a few seconds ago
Got it, that makes sense! I appreciate the details, I may have switched that up to make it easier to use a while back and never updated the documentation to reflect. I'll get that sorted asap!

•Edit•Reply•Share ›

@scrthq scrthq added the documentation update Documentation update needed for this label Jan 7, 2020
@scrthq scrthq self-assigned this Jan 7, 2020
@scrthq scrthq added this to the 2.36.0 milestone Jan 22, 2020
@scrthq scrthq mentioned this issue Feb 28, 2020
@scrthq scrthq closed this as completed in daaae47 Feb 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation update Documentation update needed for this
Projects
None yet
Development

No branches or pull requests

1 participant