NIMLocalAntiSpamResult class Null safety
Result for local anti-spam review The anti-spam lexicon is managed and configured by the developer in the CommsEase console, and the SDK can download and manage this lexicon. Three rules are applied for anti-spam hits
Client-side replacement: replace the hit anti-spam word with the specified text, then send the message with the replaced text to the server
Client-side interception: If a message is hit by anti-spam rules, this message will be dropped
Server-side processing: You can configure the message attributes as hits by server moderation, and then sends the hit message to the server. The sender can see the message being sent, but the messaging server will not deliver the message and the recipient will not receive the message. For information about how to configure the message properties, see the following.
Constructors
- NIMLocalAntiSpamResult(int operator, String? content)
-
NIMLocalAntiSpamResult.fromMap(Map<
String, dynamic> map) -
factory
Properties
- content → String?
-
The text used to replace the hit content
final
- hashCode → int
-
The hash code for this object.
read-only, inherited
- operator → int
-
The type of action for spam hits, 0: no hit; 1: client-side replacement; 2: client-side interception; 3: server-side processing.
final
- runtimeType → Type
-
A representation of the runtime type of the object.
read-only, inherited
Methods
-
noSuchMethod(
Invocation invocation) → dynamic -
Invoked when a non-existent method or property is accessed.
inherited
-
toString(
) → String -
A string representation of this object.
inherited
Operators
-
operator ==(
Object other) → bool -
The equality operator.
inherited
Constants
- clientIntercept → const int
-
Client interception
If a message is hit by anti-spam rules, this message will be dropped
2 - clientReplace → const int
-
Client replacement.
Replace the hit anti-spam word with the specified text and send the message with the replaced text to the server
1 - pass → const int
-
missing
0 - serverIntercept → const int
-
Server-side processing.
You can configure the message attributes as hits by server moderation, and then sends the hit message to the server. The sender can see the message being sent, but the messaging server will not deliver the message and the recipient will not receive the message. For information about how to configure the message properties, see the following.
3