feat: add API to check browser info #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions bot
pushed a commit
that referenced
this pull request
Oct 12, 2023
# [1.1.0](v1.0.0...v1.1.0) (2023-10-12) ### Features * add API to check browser info ([#3](#3)) ([2e92a27](2e92a27))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a
BrowserInfoclass to check certain details about the browser such as browser name and browser version.I went back and forth on whether or not these should be standalone utility functions or if they should be wrapped inside a
BrowserInfoclass. I decided on the latter for 2 reasons:WebCapabilitiesclass is currently doing.Browser.getParserto only need to be called once.