LimiterConfiguration

class LimiterConfiguration(enabled: Boolean, periodUnit: TimeUnit, period: Long, overallLimit: Int, stacktraceLimit: Int, exceptionClassLimit: Int, failedReportLimit: Int, ignoredCrashToast: String?, deleteReportsOnAppUpdate: Boolean, resetLimitsOnAppUpdate: Boolean) : Configuration

Limiter configuration

Author

F43nd1r

Since

26.10.2017

Constructors

Link copied to clipboard
fun LimiterConfiguration(enabled: Boolean = true, periodUnit: TimeUnit = TimeUnit.DAYS, period: Long = 7, overallLimit: Int = 25, stacktraceLimit: Int = 3, exceptionClassLimit: Int = 10, failedReportLimit: Int = 5, ignoredCrashToast: String? = null, deleteReportsOnAppUpdate: Boolean = true, resetLimitsOnAppUpdate: Boolean = true)

Functions

Link copied to clipboard
open override fun enabled(): Boolean

Properties

Link copied to clipboard
val deleteReportsOnAppUpdate: Boolean = true

This property can be used to determine whether old (out of date) reports should be sent or not.

Link copied to clipboard
val enabled: Boolean = true

enables this plugin

Link copied to clipboard
val exceptionClassLimit: Int = 10

limit for reports with the same exception class per period

Link copied to clipboard
val failedReportLimit: Int = 5

limit for unsent reports to keep

Link copied to clipboard
val ignoredCrashToast: String? = null

toast shown when a report was not collected or sent because a limit was exceeded

Link copied to clipboard
val overallLimit: Int = 25

general limit of reports per period

Link copied to clipboard
val period: Long = 7

number of periodUnits in which to limit reports

Link copied to clipboard
val periodUnit: TimeUnit

Unit of period

Link copied to clipboard
val resetLimitsOnAppUpdate: Boolean = true

Resetting limits after an app update allows you to see if a bug still exists.

Link copied to clipboard
val stacktraceLimit: Int = 3

limit for reports with the same stacktrace per period