Skip to content

chore: refactory string matcher #2067

@zhaohuabing

Description

@zhaohuabing

Description:

The string match types are a bit messy. They're defined in multiple APIs but look similar. For most EG APIs(Ratelimit and CORS for now, more in the future), the match types are just used to represent the StringMatcher XDS API.

What I'd like to change:

  • Create a common StringMatcher that can be used by Ratelimit, CORS, and other APIs that need plain string matching
  • Change the name of StringMatcher in Stats to avoid naming conflicting

I would like to raise a PR to refactor it if it makes sense.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions