Switch with wildcard and regex in PowerShell - Step-by-Step Execution

Concept Flow - Switch with wildcard and regex

Input value

↓

Switch statement starts

↓

Check each case

↓

Wildcard?

↓

Match?

↓

Execute case block

↓

End switch or next case

The switch statement checks the input against each case using wildcard or regex patterns, executing the matching case block.

Execution Sample

PowerShell

switch ($input) {
  "file*" { "Wildcard match: $input" }
  "regex:^data\d+$" { "Regex match: $input" }
  default { "No match" }
}

This script checks if the input matches a wildcard pattern or a regex pattern and prints the matching case.

Execution Table

Step	Input	Case Pattern	Pattern Type	Match Result	Action Taken	Output
1	file123	file*	Wildcard	Yes	Execute wildcard case	Wildcard match: file123
2	data45	file*	Wildcard	No	Check next case
3	data45	regex:^data\d+$	Regex	Yes	Execute regex case	Regex match: data45
4	test	file*	Wildcard	No	Check next case
5	test	regex:^data\d+$	Regex	No	Execute default case	No match
6	file	file*	Wildcard	Yes	Execute wildcard case	Wildcard match: file

💡 Switch ends after executing the first matching case or default if no matches.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	Final
input	N/A	file123	data45	test	file
output	N/A	Wildcard match: file123	Regex match: data45	No match	Wildcard match: file

Key Moments - 3 Insights

Why does the switch stop checking after the first match?

Because in the execution_table, once a case matches (like step 1 or 3), the switch executes that case and exits without checking further cases.

How does the switch know to treat a pattern as regex?

The pattern starting with 'regex:' tells the switch to treat the rest as a regex pattern, as shown in steps 3 and 5 in the execution_table.

What happens if no cases match?

The default case runs, as shown in step 5 where input 'test' matches no patterns, so 'No match' is output.

Visual Quiz - 3 Questions

Look at the execution_table, what output is produced at step 3?

A Regex match: data45

B Wildcard match: data45

C No match

D Wildcard match: file123

💡 Hint

Check the 'Output' column for step 3 in the execution_table.

At which step does the switch execute the default case?

A Step 1

B Step 5

C Step 3

D Step 6

💡 Hint

Look for 'Execute default case' in the 'Action Taken' column.

If the input is 'file', which case matches according to the execution_table?

A Regex case

B Default case

C Wildcard case

D No case matches

💡 Hint

See step 6 where input 'file' matches 'file*' wildcard pattern.

Concept Snapshot

switch ($input) {
  "pattern*" { action }
  "regex:pattern" { action }
  default { action }
}
- Checks cases in order
- Wildcard matches simple patterns
- regex: prefix uses regex
- Stops at first match
- default runs if no match

Full Transcript

This visual execution shows how a PowerShell switch statement uses wildcard and regex patterns to match input values. The switch checks each case in order. If the input matches a wildcard pattern like 'file*', it runs that case and stops. If not, it checks regex patterns marked with 'regex:'. If no cases match, the default case runs. The execution table traces inputs like 'file123', 'data45', and 'test' through the cases, showing which matches and what output is produced. Variables like input and output change as the switch runs. Key moments clarify why the switch stops after the first match, how regex patterns are recognized, and what happens when no match occurs. The quiz tests understanding of outputs at specific steps and case matching behavior.

Practice

1. What does the -Wildcard parameter do in a PowerShell switch statement?

easy

A. It matches patterns using complex regular expressions.

B. It makes the switch statement run faster by skipping checks.

C. It forces the switch to ignore case sensitivity.

D. It matches patterns using simple wildcards like * and ?.

Solution

1. Step 1: Understand the role of -Wildcard

   The -Wildcard parameter allows pattern matching using simple wildcards such as * (any characters) and ? (single character).

2. Step 2: Differentiate from -Regex

   Unlike -Regex, which uses complex regular expressions, -Wildcard is simpler and easier for basic pattern matching.

3. Final Answer:

   It matches patterns using simple wildcards like * and ?. -> Option D

4. Quick Check:

   -Wildcard = simple wildcard matching [OK]

Hint: Remember: Wildcard = * and ? patterns, Regex = complex patterns [OK]

Common Mistakes:

• Confusing -Wildcard with -Regex
• Thinking -Wildcard ignores case by default
• Assuming -Wildcard speeds up execution

2. Which of the following is the correct syntax to use a switch statement with wildcard matching in PowerShell?

easy

A. switch ($input) { '*test*' -Wildcard { 'Match' } }

B. switch ($input) -Wildcard { '*test*' { 'Match' } }

C. switch -Wildcard ($input) { '*test*' { 'Match' } }

D. switch ($input) { -Wildcard '*test*' { 'Match' } }

Solution

1. Step 1: Identify correct parameter placement

   In PowerShell, the -Wildcard parameter is placed immediately after switch and before the input expression.

2. Step 2: Check the pattern and block syntax

   The pattern '*test*' and the script block '{ 'Match' }' are correctly placed inside the switch braces.

3. Final Answer:

   switch -Wildcard ($input) { '*test*' { 'Match' } } -> Option C

4. Quick Check:

   Parameter right after switch keyword = switch -Wildcard ($input) { '*test*' { 'Match' } } [OK]

Hint: Put -Wildcard right after switch, before input [OK]

Common Mistakes:

• Placing -Wildcard inside the switch block
• Putting -Wildcard after the input variable
• Using -Wildcard as a pattern inside braces

3. What will be the output of this PowerShell code?

switch -Regex ('apple', 'banana', 'cherry') {
  '^a' { 'Starts with a' }
  'an' { 'Contains an' }
  default { 'No match' }
}

medium

A. Starts with a
Contains an
No match

B. Starts with a
No match
No match

C. No match
Contains an
No match

D. Starts with a
Contains an
Contains an

Solution

1. Step 1: Check each input against regex patterns

   'apple' matches '^a' (starts with 'a'), so outputs 'Starts with a'. 'banana' contains 'an', so matches 'an' pattern, outputs 'Contains an'. 'cherry' matches none, so outputs 'No match'.

2. Step 2: Confirm output order

   The outputs correspond to each input in order: 'apple' -> 'Starts with a', 'banana' -> 'Contains an', 'cherry' -> 'No match'.

3. Final Answer:

   Starts with a Contains an No match -> Option A

4. Quick Check:

   Regex matches each input correctly = Starts with a Contains an No match [OK]

Hint: Match each input line by line with regex patterns [OK]

Common Mistakes:

• Assuming only first match per input
• Confusing regex anchors like ^
• Ignoring default case output

4. Identify the error in this PowerShell switch statement using wildcard matching:

switch ($word) -Wildcard {
  'he*' { 'Starts with he' }
  '*lo' { 'Ends with lo' }
  default { 'No match' }
}

medium

A. The -Wildcard parameter should be before the input variable.

B. The patterns 'he*' and '*lo' are invalid wildcards.

C. The default case is missing a script block.

D. The switch statement cannot use wildcards with variables.

Solution

1. Step 1: Check parameter placement

   The -Wildcard parameter must come immediately after the switch keyword, not after the input variable.

2. Step 2: Validate patterns and default block

   The patterns 'he*' and '*lo' are valid wildcards. The default case has a proper script block. Using wildcards with variables is allowed.

3. Final Answer:

   The -Wildcard parameter should be before the input variable. -> Option A

4. Quick Check:

   Parameter placement error = The -Wildcard parameter should be before the input variable. [OK]

Hint: Place -Wildcard right after switch, before input variable [OK]

Common Mistakes:

• Putting -Wildcard after input variable
• Thinking wildcards are invalid patterns
• Omitting script block braces

5. You want to categorize a list of filenames using switch with both wildcard and regex patterns. Which approach correctly combines -Wildcard and -Regex in one script to handle different patterns?

hard

A. Use a single switch with both -Wildcard and -Regex parameters together.

B. Use two separate switch statements: one with -Wildcard, one with -Regex, processing the list twice.

C. Use -Wildcard and -Regex as pattern modifiers inside one switch statement.

D. Use -Regex only and convert wildcards to regex patterns manually.

Solution

1. Step 1: Understand parameter exclusivity

   PowerShell's switch does not support using -Wildcard and -Regex together in one statement. They are mutually exclusive parameters.

2. Step 2: Choose practical approach

   To handle both wildcard and regex patterns, use two separate switch statements: one with -Wildcard and one with -Regex, processing the list twice.

3. Final Answer:

   Use two separate switch statements: one with -Wildcard, one with -Regex, processing the list twice. -> Option B

4. Quick Check:

   Separate switches for wildcard and regex = Use two separate switch statements: one with -Wildcard, one with -Regex, processing the list twice. [OK]

Hint: Use separate switches for wildcard and regex patterns [OK]

Common Mistakes:

• Trying to combine -Wildcard and -Regex in one switch
• Assuming pattern modifiers inside switch block
• Converting wildcards manually instead of separate switches