Provide read-only access to some properties generated inside tracker object
See original GitHub issueRecentrly we encountered few cases where users wanted to get some properties that are encapsulated inside tracker object. Particularly, users wanted to get cookieDomain
and pageViewId
to use in app logic. It’s possible to get cookieDomain
with lengthy script, but seems not possible at all for pageViewId
.
I think we should provide some read-only access to at least these properties (and may be consider another properties) as getter-functions.
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (11 by maintainers)
Top Results From Across the Web
Control Access to Objects Unit - Trailhead - Salesforce
The simplest way to control data access is to set permissions on a particular type of object. (An object is a collection of...
Read more >Data access and editing—ArcGIS Online Help | Documentation
What if you want some people to edit but not others? Can you keep track of who edits your data? Do you need...
Read more >Tracking vs. No-Tracking Queries - EF Core | Microsoft Learn
No tracking queries are useful when the results are used in a read-only scenario. They're quicker to execute because there's no need to...
Read more >HTML attribute: readonly - HTML: HyperText Markup Language
If the element is read-only, then the element's value can not be updated by the user, and does not participate in constraint validation....
Read more >Read-only role - ServiceNow Docs
The read-only role (snc_read_only) restricts a user or a group of users to read-only access on the tables to which the user already...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yes
cookieName
andpageViewId
have been exposed in 2.8.x (cf #574 and #575)Okay let’s go for it, it can’t hurt…