Cron Step Value Extraction Regex for Go
/(?:\*|[0-9]{1,2}(?:-[0-9]{1,2})?)/([1-9][0-9]?)/gWhat this pattern does
This page provides a well-structured, multi-part regular expression for matching cron step value extraction, ported and verified for Go. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Go project — whether you're validating in a Gin handler, a gRPC service, or a command-line tool.
Go Implementation
// Cron Step Value Extraction
// ReDoS-safe | RegexVault — Dev & Systems > Cron
package validation
import "regexp"
var cronStepValueExtractionRe = regexp.MustCompile(`(?:\*|[0-9]{1,2}(?:-[0-9]{1,2})?)/([1-9][0-9]?)`)
func ValidateCronStepValueExtraction(s string) bool {
return cronStepValueExtractionRe.MatchString(s)
}
// Example
// fmt.Println(ValidateCronStepValueExtraction("*/15")) // trueTest Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
*/15 | /5 |
0-59/5 | */ |
*/2 | */ 5 |
0-23/6 | */0 |
1-31/7 | * * * * * |
When to use this pattern
This pattern is drawn from the Dev & Systems > Cron category and carries a ReDoS-safe certification. That matters for Go developers because Go's RE2 engine is inherently safe from catastrophic backtracking, but this pattern has been additionally verified for correctness. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.
Common Pitfalls
A bare /5 without a base value is invalid in all cron implementations. Always validate that a base field precedes the slash.
Technical Notes
Capture group 1 contains the step value. Used for programmatic extraction of schedule frequency. A step must always follow either * or a range.
Have a pattern that belongs in the vault?
Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.
Submit a Pattern