Added postToTopic() for MessagingService needs

[commonly-ts]

Requires user to have set their API key. The API key requires access permission Messaging Service API and its operation Publish.

Use case example:

// JavaScript

const noblox = require("noblox.js")

await noblox.setAPIKey(process.env.API_KEY)

const universeId = 4283343407
const topicName = "ModerateUser"
const data = { targetUser: 123456789, staffMember: 1210019099, action: "Kick" }

await noblox.publishToTopic(universeId, topicName, data)

-- Roblox Luau

local MessagingService = game:GetService("MessagingService")
local HttpService = game:GetService("HttpService")

MessagingService:SubscribeAsync("ModerateUser", function(message)
    -- The information passed in the JavaScript is placed into `Data` and needs to be decoded
    -- Types can be used here to parse the decoded data
    local data = HttpService:JSONDecode(message.Data)
	
    print(data)
end)

Roblox documentation:
https://create.roblox.com/docs/reference/cloud/messaging-service
https://create.roblox.com/docs/cloud/open-cloud/usage-messaging

[nottisa]

Thank you for contributing! I currently don't have that much time to test. I will test sooner or later.

[nottisa]

Error handling should probably be handled like in this file: lib/friends/acceptFriendRequest.js. If I'm wrong, you don't actually need the format string and can just manually enter the error codes which might be slightly more performant.

[commonly-ts]

I made a later commit to replace the switch case with just an if else.
I'm not sure what you mean that I don't need to format the string? - ah I know what you mean, yeah that could be done instead.

[nottisa]

I just mean errors should probably be reported as they come from Roblox, and not what we currently understand those errors to be. The file I linked has dynamic error handling that should pull the errors from the API instead of being hard coded in. I saw the later commit, I think it would just be in our best interest to pull the errors directly from Roblox.

[commonly-ts]

Alright, I completely agree. I'll make a commit for the errors to be handled like they are in acceptFriendRequest.

[commonly-ts]

Error handling is now updated to give proper errors. The errors this API returns are very different than others so I had to spent a little more time figuring them out.

Valid API key that has any sort of invalid access permissions/scopes will return:
Error: [403] InsufficientScope Scope not authorized.

Invalid API key will return:
Error: [401] Unauthorized Invalid API Key

[nottisa]

Looks good. I'll try and test it in the next couple days.

[Neztore]

Nottisa mentioned no longer being able to contribute to the library (I assume due to other commitments), so I am reviewing.. I am happy to merge this once the typings are updated (https://github.com/noblox/noblox.js/tree/master/typings) but the way we handle open cloud may change after tomorrows meeting.

[commonly-ts]

I am happy to merge this once the typings are updated (https://github.com/noblox/noblox.js/tree/master/typings)

I have committed the change to the typings. Unsure why it also committed changes to whitespace removal 🤷