Meteor-Community-Packages/meteor-user-status

Request: Break down the userAgent string for easy aggregation

Open

#100 opened on May 19, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (560 stars) (86 forks)batch import
good first issue

Description

I'd love to see the UserAgent string broken down into more fields. This would allow a developer to easily write queries and aggregations based on the different parts of the string. I'd love to use this to see how many users are on a particular platform. But right now this is difficult because if a user happens to use safari/601.1 and another uses safari 600.1, these strings are considered separate even though the browser is still Safari.

Based on the Wikipedia explanation of the different parts, you could have

userAgent: {
  fullString: 'Mozilla/5.0 (iPad; U; CPU OS 3_2_1 like Mac OS X; en-us) AppleWebKit/531.21.10 (KHTML, like Gecko) Mobile/7B405',
  systemDetails: 'iPad; U; CPU OS 3_2_1 like Mac OS X; en-us',
  browserPlatform: {
    name: 'AppleWebKit'
    version: '531.21.10',
  }
  browserPlatformDetails: 'KHTML, like Gecko',
  enhancements: 'Mobile/7B405',
}

Contributor guide

Tech stack
javascriptnodejs
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic JavaScriptFamiliarity with MeteorUnderstanding of user agent strings
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the current user status schema in the Meteor package (likely in a file like 'schema.js' or 'user status.js') to see how the userAgent field is currently stored. Implement a function to parse the User Agent string into the proposed sub fields, ensuring backward compatibility. Add tests to verify the parsing logic and update any documentation or queries that rely on the raw userAgent string.