Code collector manual#
Code collector skin#
Code collector code#

It is also disabled as long as there are validation errors (marked by red messages near the invalid entry in the form). The Submit button is disabled until all required entries (marked by an asterisk after the label) are populated. While filling out the form, mobile workers must provide required information as well as resolve any validation errors.

These should be reviewed before submission. Use default values prepopulated in the form.Scan barcodes and QR codes to simplify data entry and avoid typos.Attach photos and videos to provide visual information.

Code collector manual#

In addition to manual entry of values, mobile workers can do the following to simplify data entry: It will also check that the person who reacted shares the same id as the author of the original message that the collector was assigned to.Fill out the form for each asset, observation, and inspection done in the field.

Code collector skin#

The filter will check for the 👍 emoji–in the default skin tone specifically, so be wary of that. This example uses the Message#createReactionCollector() open in new window method. These work quite similarly to message collectors, except that you apply them on a message rather than a channel. # Reaction collectors # Basic reaction collector As you can see, there is no collect event, so you are limited in that regard. The errors section specifies that time will cause it to error out, which will cause the Promise to reject if one correct answer is not received within the time limit of one minute.

The options (the second parameter) specifies that only a maximum of one message can go through the filter successfully before the Promise successfully resolves. The filter looks for messages that match one of the answers in the array of possible answers to pass through the collector. In the options section, you only want to allow one answer to pass through, hence the max: 1 setting. You would like to ignore the case because simple typos can happen, so you convert each answer to its lowercase form and check if it's equal to the response in lowercase form as well. In this filter, you iterate through the answers to find what you want. some() works, you can read about it in more detail here open in new window. awaitMessages() feature.įirst, you'll need some questions and answers to choose from, so here's a basic set: Instead of taking their example, let's set up a basic quiz command using the. However, it should do for most purposes, such as awaiting the correct response in a quiz. However, the drawback of using this method is that you cannot do things before the Promise is resolved or rejected, either by an error or completion. It is essentially identical to TextChannel#createMessageCollector() open in new window, except promisified.

Code collector code#

Using TextChannel#awaitMessages() open in new window can be easier if you understand Promises, and it allows you to have cleaner code overall. You can also stop the collector manually by calling collector.stop(). awaitMessages() (its promise-based counterpart) is that you can do something directly after each message is collected, rather than just after the collector ended. The benefit of using an event-based collector over.

maxProcessed: Number of messages encountered (no matter the filter result).

max: Number of messages to successfully pass the filter.

time: Amount of time in milliseconds the collector should run for.

You can control when a collector ends by supplying additional option keys when creating a collector: Once the collector finishes collecting based on the provided end conditions the end event emits. In the above example, you simply log the message.

This message is then passed into the event listener as collected and the provided function is executed. If a message passes through the filter, it will trigger the collect event for the collector you've created. Note that the above example uses implicit return open in new window for the filter function and passes it to the options object using the object property shorthand open in new window notation. If you don't provide a filter all messages in the channel the collector was started on will be collected. To check for multiple conditions in your filter you can connect them using logical operators open in new window. The value to this key should be a function that returns a boolean value to indicate if this message should be collected or not. You can provide a filter key to the object parameter of createMessageCollector().

Image manipulation with Parsing mentions.