Test: chatdisabledProcessor

[deeola]

Description

Unit test for ChatDisabledProcessor

Closes #(issue)

#169

Please select the relevant option(s).

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (changes to docs/code comments)

What is the proposed approach?

Tested for the following

• Do nothing is block.chatDisabled is null
• Call setTextAreaDisabled with the boolean value if block.chatDisabled is a boolean
• Call setTextAreaDisabled with the return value of a function if block.chatDisabled is a function
• Await the promise if block.chatDisabled is a function that returns a promise
• Call setTextAreaDisabled with null if block.chatDisabled is a function returning null
• Handle errors when block.chatDisabled function throws an error
• Handle promise rejection if block.chatDisabled function returns a rejected promise
• Handle unexpected data type for block.chatDisabled (e.g., an object)

Checklist:

• The commit message follows our adopted guidelines
• Testing has been done for the change(s) added (for bug fixes/features)
• Relevant comments/docs have been added/updated (for bug fixes/features)

[tjtanjin]

Is there a specific reason this was added? For chatDisabled, it should only take in a boolean value or a function that returns a boolean value.

[tjtanjin]

We don't expect block.chatDisabled to be null, so the Block type shouldn't be updated.