Custom rules
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 4.9k
- Forks
- 546
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
We have native mobile applications. These apps send some tiny header data, for example `okhttp/$libraryVersion` for Android and `$appName/$appVersion ($appPackage; build:$appBuildNumber; iOS 13.5.1) Alamofire/$libraryVersion` for iOS.
It could be useful to add some custom rules, that can be fallbacked in case there is no response from regular rules, but didnt find it in codebase. Any suggestions?
Thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the parser currently handles regular user-agent rules and where a fallback could accept custom rules. Clarify the configuration format and precedence for Android and iOS headers, then verify parsing for the okhttp and Alamofire examples in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100