From ca527cc4c0afb1c0426a1387e9d9fb0300a44c88 Mon Sep 17 00:00:00 2001 From: Travis Eden Date: Thu, 14 Dec 2017 16:12:04 -0500 Subject: [PATCH 1/7] Make Discover page channel names into links --- src/renderer/component/fileCard/view.jsx | 10 +++++--- src/renderer/component/link/view.jsx | 26 +++++++++++--------- src/renderer/component/uriIndicator/view.jsx | 3 ++- 3 files changed, 23 insertions(+), 16 deletions(-) diff --git a/src/renderer/component/fileCard/view.jsx b/src/renderer/component/fileCard/view.jsx index 00a42eb29..a7ec6a5fa 100644 --- a/src/renderer/component/fileCard/view.jsx +++ b/src/renderer/component/fileCard/view.jsx @@ -94,20 +94,22 @@ class FileCard extends React.PureComponent { {title}
- + {" "} {isRewardContent && }{" "} {fileInfo && } - + + +
- {/* Test for nizuka's design: should we remove description? + + {/* Test for nizuka's design: should we remove description?
{description}
*/} - {obscureNsfw && this.state.hovered && } diff --git a/src/renderer/component/link/view.jsx b/src/renderer/component/link/view.jsx index cfb2a731b..0f5ea3fca 100644 --- a/src/renderer/component/link/view.jsx +++ b/src/renderer/component/link/view.jsx @@ -16,6 +16,7 @@ const Link = props => { navigateParams, doNavigate, className, + span, } = props; const combinedClassName = @@ -26,7 +27,8 @@ const Link = props => { const onClick = !props.onClick && navigate - ? () => { + ? e => { + e.stopPropagation(); doNavigate(navigate, navigateParams || {}); } : props.onClick; @@ -44,16 +46,18 @@ const Link = props => { ); } - return ( - - {content} - + const linkProps = { + className: combinedClassName, + href: href || "javascript:;", + title, + onClick, + style, + }; + + return span ? ( + {content} + ) : ( + {content} ); }; diff --git a/src/renderer/component/uriIndicator/view.jsx b/src/renderer/component/uriIndicator/view.jsx index 3bf850d11..60b912e35 100644 --- a/src/renderer/component/uriIndicator/view.jsx +++ b/src/renderer/component/uriIndicator/view.jsx @@ -22,7 +22,7 @@ class UriIndicator extends React.PureComponent { } render() { - const { claim, link, uri, isResolvingUri, smallCard } = this.props; + const { claim, link, uri, isResolvingUri, smallCard, span } = this.props; if (isResolvingUri && !claim) { return Validating...; @@ -91,6 +91,7 @@ class UriIndicator extends React.PureComponent { navigate="/show" navigateParams={{ uri: channelLink }} className="no-underline" + span={span} > {inner} -- 2.45.3 From c4c43e1219d862b00658c6c704713aab7cd46399 Mon Sep 17 00:00:00 2001 From: Igor Gassmann Date: Fri, 15 Dec 2017 17:33:01 -0300 Subject: [PATCH 2/7] Add linux app category --- electron-builder.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/electron-builder.json b/electron-builder.json index acf8e77a2..9e0a8f86b 100644 --- a/electron-builder.json +++ b/electron-builder.json @@ -1,7 +1,7 @@ { "appId": "io.lbry.LBRY", "mac": { - "category": "public.app-category.entertainment", + "category": "public.app-category.entertainment" }, "dmg": { "iconSize": 128, @@ -34,6 +34,7 @@ ], "linux": { "target": "deb", + "category": "Video", "desktop": { "MimeType": "x-scheme-handler/lbry", "Exec": "/opt/LBRY/lbry %U" -- 2.45.3 From 1d67f8df9cb36f66deed9a5522266c34193103f2 Mon Sep 17 00:00:00 2001 From: Jeremy Kauffman Date: Fri, 15 Dec 2017 15:46:50 -0500 Subject: [PATCH 3/7] add copy button to wallet address, fixes #875 --- CHANGELOG.md | 2 +- src/renderer/component/walletAddress/view.jsx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e66e97c3e..7a57edac4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,7 +8,7 @@ Web UI version numbers should always match the corresponding version of LBRY App ## [Unreleased] ### Added - * + * Added copy address button to the Wallet Address component on Send / Receive (#875) * ### Changed diff --git a/src/renderer/component/walletAddress/view.jsx b/src/renderer/component/walletAddress/view.jsx index 829955fa6..72bb91a46 100644 --- a/src/renderer/component/walletAddress/view.jsx +++ b/src/renderer/component/walletAddress/view.jsx @@ -21,7 +21,7 @@ class WalletAddress extends React.PureComponent { "Use this wallet address to receive credits sent by another user (or yourself)." )}

-
+
Date: Fri, 15 Dec 2017 21:12:59 -0800 Subject: [PATCH 4/7] Updated contribution process --- CONTRIBUTING.md | 36 +++++++++++++++++++++++++++++++++++- 1 file changed, 35 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e7d0dce20..a64256fb0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,3 +1,37 @@ ## Contributing to LBRY -https://lbry.io/faq/contributing +You found this page! That means you are well on your way to contributing to the LBRY app. This application is primarily written in JavaScript and is built on [Electron](https://electronjs.org) while utilizing [React](https://reactjs.org) and [Redux](https://redux.js.org) for UI and application state. + +LBRY is an open source project, and therefore is developed out in the open for everyone to see. What you see here are the latest source code changes and the issues. + +Since LBRY is an based around a decentralized community, we believe that the app will be strongest if it receives contributions from individuals outside the core team -- such as yourself! + +In order to make contributing as easy and rewarding of possible, we have instituted the following system: + +* Anyone can view all issues in the system by clicking on the [Issues](https://github.com/lbryio/lbry-app/issues) button at the top of the page. +...Feel free to add an issue if you think we have missed something (and you might earn some LBC in the process because we do tip people for reporting bugs). +* Once on the [Issues](https://github.com/lbryio/lbry-app/issues) page, a user can filter issues by the [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) label to see a curated list of suggested issues with which community members can help. +* Every [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) issue is ranked on a scale from zero to four. +...--- | --- +...[**level 0**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+0%22) | Typos and text edit -- a tech savvy non-programmer can fix these +...[**level 1**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+1%22) | Programming issues that require little knowledge of how the LBRY app works +...[**level 2**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+2%22) | Issues of average difficulty that require the developer to dig into how the app works a little bit +...[**level 3**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+3%22) | Issues that are likely too tricky to be level 2 or require more thinking outside of the box +...[**level 4**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+4%22) | Big features or really hard issues +...The process of ranking issues is highly subjective. The purpose of sorting issues like this is to give contributors a general idea of the type of issues at which they are looking. It could very well be the case that a level 1 issue is more difficult than a level 2, for instance. This system is meant to help you find relevant issues, not to prevent you from working on issues that you otherwise would. If these rankings don't work for you, feel free to ignore them. +* After deciding what to work on, [fork](https://help.github.com/articles/fork-a-repo/) this repository, make your changes, and submit a [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/). +* Once your pull request is visible in the LBRY repo, a LBRY team member will review it and make sure it is up to our standards. At this point, you may have to change your code based on our suggestions and comments. +* Then, upon a satisfactory review your code, we will merge it and send you a tip (in LBC) for your contribution. + +We are dedicated to be fair and friendly in this process. In __general__, level 4 issues will be paid more than level 3 issues which will be paid more than level 2, and so on. However, this is not due to their labels, but rather how difficult they ended up being. Maybe an issue was labeled level 1 but was actually very difficult-- in this case we would be **more than happy** to tip accordingly. If you do good work, we want you to be rewarded for it. + +Also, we are here to enable you. We want you to succeed, so do not hesitate to ask questions. If you need some information or assistance in completely an issue, please let us know! This is what we are here for-- pushing development forward. + +Lastly, don't feel limited by this list. Should LBRY have built in VPN/proxy support? Add it! It's not in the issue tracker but maybe it's a good idea. Do you think the search layout is unintuitive? Change it! We welcome all feedback and suggestions. That said, it may be the case that we do not wish to incorporate your change, if you don't check with us first. If you want to add a feature that is not listed in the issue tracker, go ahead and [create an issue](https://github.com/lbryio/lbry-app/issues/new), and say in the description that you would like to try to implement it yourself. This way we can tell you in advance if we will accept your changes and we can point you in the right direction. + +## Get In Touch +[Liam](https://github.com/liamcardenas) is the application engineer in charge of community development. He is the person to contact with any development/contribution related questions. Discord: liamsdouble, Email: liam@lbry.io +[Tom](https://github.com/tzarebczan) is the community manager. He knows more than anyone about the app and all of its flaws. Reach out to him with any questions about how the app works, if a bug has been reported, or if a feature should be requested. Discord: jigglytom, Email: tom@lbry.io +[Sean](https://github.com/seanyesmunt) is an application engineer who focuses largely on UI/UX. If you have a design or implementation question, feel free to reach out to him. Discord: sean, Email: sean@lbry.io + +More information about contributing to LBRY [here](https://lbry.io/faq/contributing). -- 2.45.3 From 8d28babaf1fa5d1a8722cf52442f1f2f67201573 Mon Sep 17 00:00:00 2001 From: Liam Cardenas Date: Fri, 15 Dec 2017 21:42:55 -0800 Subject: [PATCH 5/7] Fixed typos and formatting issues --- CONTRIBUTING.md | 53 +++++++++++++++++++++++++++++-------------------- 1 file changed, 31 insertions(+), 22 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a64256fb0..e9d7c9811 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,37 +1,46 @@ -## Contributing to LBRY +# Contributing to LBRY You found this page! That means you are well on your way to contributing to the LBRY app. This application is primarily written in JavaScript and is built on [Electron](https://electronjs.org) while utilizing [React](https://reactjs.org) and [Redux](https://redux.js.org) for UI and application state. -LBRY is an open source project, and therefore is developed out in the open for everyone to see. What you see here are the latest source code changes and the issues. +LBRY is an open source project, and therefore is developed out in the open for everyone to see. What you see here are the latest source code changes and issues. Since LBRY is an based around a decentralized community, we believe that the app will be strongest if it receives contributions from individuals outside the core team -- such as yourself! In order to make contributing as easy and rewarding of possible, we have instituted the following system: -* Anyone can view all issues in the system by clicking on the [Issues](https://github.com/lbryio/lbry-app/issues) button at the top of the page. -...Feel free to add an issue if you think we have missed something (and you might earn some LBC in the process because we do tip people for reporting bugs). -* Once on the [Issues](https://github.com/lbryio/lbry-app/issues) page, a user can filter issues by the [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) label to see a curated list of suggested issues with which community members can help. +* Anyone can view all issues in the system by clicking on the [Issues](https://github.com/lbryio/lbry-app/issues) button at the top of the page. Feel free to add an issue if you think we have missed something (and you might earn some LBC in the process because we do tip people for reporting bugs). +* Once on the [Issues](https://github.com/lbryio/lbry-app/issues) page, a potential contributor can filter issues by the [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) label to see a curated list of suggested issues with which community members can help. * Every [Help Wanted](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) issue is ranked on a scale from zero to four. -...--- | --- -...[**level 0**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+0%22) | Typos and text edit -- a tech savvy non-programmer can fix these -...[**level 1**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+1%22) | Programming issues that require little knowledge of how the LBRY app works -...[**level 2**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+2%22) | Issues of average difficulty that require the developer to dig into how the app works a little bit -...[**level 3**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+3%22) | Issues that are likely too tricky to be level 2 or require more thinking outside of the box -...[**level 4**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+4%22) | Big features or really hard issues -...The process of ranking issues is highly subjective. The purpose of sorting issues like this is to give contributors a general idea of the type of issues at which they are looking. It could very well be the case that a level 1 issue is more difficult than a level 2, for instance. This system is meant to help you find relevant issues, not to prevent you from working on issues that you otherwise would. If these rankings don't work for you, feel free to ignore them. -* After deciding what to work on, [fork](https://help.github.com/articles/fork-a-repo/) this repository, make your changes, and submit a [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/). -* Once your pull request is visible in the LBRY repo, a LBRY team member will review it and make sure it is up to our standards. At this point, you may have to change your code based on our suggestions and comments. -* Then, upon a satisfactory review your code, we will merge it and send you a tip (in LBC) for your contribution. -We are dedicated to be fair and friendly in this process. In __general__, level 4 issues will be paid more than level 3 issues which will be paid more than level 2, and so on. However, this is not due to their labels, but rather how difficult they ended up being. Maybe an issue was labeled level 1 but was actually very difficult-- in this case we would be **more than happy** to tip accordingly. If you do good work, we want you to be rewarded for it. +Level | Description +--- | --- +[**level 0**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+0%22) | Typos and text edits -- a tech savvy non-programmer can fix these +[**level 1**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+1%22) | Programming issues that require little knowledge of how the LBRY app works +[**level 2**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+2%22) | Issues of average difficulty that require the developer to dig into how the app works a little bit +[**level 3**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+3%22) | Issues that are likely too tricky to be level 2 or require more thinking outside of the box +[**level 4**](https://github.com/lbryio/lbry-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22+label%3A%22level+4%22) | Big features or really hard issues -Also, we are here to enable you. We want you to succeed, so do not hesitate to ask questions. If you need some information or assistance in completely an issue, please let us know! This is what we are here for-- pushing development forward. +The process of ranking issues is highly subjective. The purpose of sorting issues like this is to give contributors a general idea of the type of issues at which they are looking. It could very well be the case that a level 1 issue is more difficult than a level 2, for instance. This system is meant to help you find relevant issues, not to prevent you from working on issues that you otherwise would. If these rankings don't work for you, feel free to ignore them. -Lastly, don't feel limited by this list. Should LBRY have built in VPN/proxy support? Add it! It's not in the issue tracker but maybe it's a good idea. Do you think the search layout is unintuitive? Change it! We welcome all feedback and suggestions. That said, it may be the case that we do not wish to incorporate your change, if you don't check with us first. If you want to add a feature that is not listed in the issue tracker, go ahead and [create an issue](https://github.com/lbryio/lbry-app/issues/new), and say in the description that you would like to try to implement it yourself. This way we can tell you in advance if we will accept your changes and we can point you in the right direction. +* After deciding what to work on, a potential contributor can [fork](https://help.github.com/articles/fork-a-repo/) this repository, make his or her changes, and submit a [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/). +* Once the pull request is visible in the LBRY repo, a LBRY team member will review it and make sure it is up to our standards. At this point, the contributor may have to change his or her code based on our suggestions and comments. +* Then, upon a satisfactory review of the code, we will merge it and send the contributor a tip (in LBC) for the contribution. -## Get In Touch -[Liam](https://github.com/liamcardenas) is the application engineer in charge of community development. He is the person to contact with any development/contribution related questions. Discord: liamsdouble, Email: liam@lbry.io -[Tom](https://github.com/tzarebczan) is the community manager. He knows more than anyone about the app and all of its flaws. Reach out to him with any questions about how the app works, if a bug has been reported, or if a feature should be requested. Discord: jigglytom, Email: tom@lbry.io -[Sean](https://github.com/seanyesmunt) is an application engineer who focuses largely on UI/UX. If you have a design or implementation question, feel free to reach out to him. Discord: sean, Email: sean@lbry.io +We are dedicated to being fair and friendly in this process. In __general__, level 4 issues will be paid more than level 3 issues which will be paid more than level 2, and so on. However, this is not due to their labels, but rather how difficult they ended up being. Maybe an issue labeled "level 1" turned out to be very difficult. In this case we would be **more than happy** to tip accordingly. If you do good work, we want you to be rewarded for it. + +Also, we are here to enable you. We want you to succeed, so do not hesitate to ask questions. If you need some information or assistance in completing an issue, please let us know! That is what we are here for-- pushing development forward. + +Lastly, don't feel limited by this list. Should LBRY have built-in Tor support? Add it! It's not in the issue tracker but maybe it's a good idea. Do you think the search layout is unintuitive? Change it! We welcome all feedback and suggestions. That said, it may be the case that we do not wish to incorporate your change if you don't check with us first (also, please check with us especially if you are planning on adding Tor support :P). If you want to add a feature that is not listed in the issue tracker, go ahead and [create an issue](https://github.com/lbryio/lbry-app/issues/new), and say in the description that you would like to try to implement it yourself. This way we can tell you in advance if we will accept your changes and we can point you in the right direction. + +# Get In Touch +Name | Role | Discord | Email +--- | --- | --- | --- +[Liam](https://github.com/liamcardenas) | The application engineer in charge of community development. He is the person to contact with any development/contribution related questions. | liamsdouble | liam@lbry.io +[Tom](https://github.com/tzarebczan) | Community manager. He knows more than anyone about the app and all of its flaws. Reach out to him with any questions about how the app works, if a bug has been reported, or if a feature should be requested. | jigglytom | tom@lbry.io +[Sean](https://github.com/seanyesmunt) | An application engineer who focuses largely on UI/UX. If you have a design or implementation question, feel free to reach out to him. | sean | sean@lbry.io + +Join our discord [here](https://chat.lbry.io/). + +# More Information More information about contributing to LBRY [here](https://lbry.io/faq/contributing). -- 2.45.3 From f407cd91a13f5b5ca2f625434824480abcf36936 Mon Sep 17 00:00:00 2001 From: Liam Cardenas Date: Mon, 18 Dec 2017 21:53:01 -0800 Subject: [PATCH 6/7] Move analytics out of redux folder --- src/renderer/index.js | 20 ++++++++++++++++---- src/renderer/redux/actions/navigation.js | 3 --- 2 files changed, 16 insertions(+), 7 deletions(-) diff --git a/src/renderer/index.js b/src/renderer/index.js index 155278bda..d5154b084 100644 --- a/src/renderer/index.js +++ b/src/renderer/index.js @@ -19,8 +19,10 @@ const contextMenu = remote.require("./main.js").contextMenu; const app = require("./app"); // Workaround for https://github.com/electron-userland/electron-webpack/issues/52 -if (process.env.NODE_ENV !== 'development') { - window.staticResourcesPath = require("path").join(remote.app.getAppPath(), "../static").replace(/\\/g, "\\\\"); +if (process.env.NODE_ENV !== "development") { + window.staticResourcesPath = require("path") + .join(remote.app.getAppPath(), "../static") + .replace(/\\/g, "\\\\"); } else { window.staticResourcesPath = ""; } @@ -55,6 +57,16 @@ ipcRenderer.on("window-is-focused", (event, data) => { dock.setBadge(""); }); +(function(history) { + var replaceState = history.replaceState; + history.replaceState = function(_, __, path) { + amplitude + .getInstance() + .logEvent("NAVIGATION", { destination: path ? path.slice(1) : path }); + return replaceState.apply(history, arguments); + }; +})(window.history); + document.addEventListener("click", event => { var target = event.target; while (target && target !== document) { @@ -110,7 +122,7 @@ var init = function() {
, - document.getElementById('app') + document.getElementById("app") ); } ); @@ -124,7 +136,7 @@ var init = function() { , - document.getElementById('app') + document.getElementById("app") ); } }; diff --git a/src/renderer/redux/actions/navigation.js b/src/renderer/redux/actions/navigation.js index a4cbca615..b718936aa 100644 --- a/src/renderer/redux/actions/navigation.js +++ b/src/renderer/redux/actions/navigation.js @@ -9,7 +9,6 @@ import { } from "redux/selectors/navigation"; import { doSearch } from "redux/actions/search"; import { toQueryString } from "util/query_params"; -import amplitude from "amplitude-js"; export function doNavigate(path, params = {}, options = {}) { return function(dispatch, getState) { @@ -24,8 +23,6 @@ export function doNavigate(path, params = {}, options = {}) { const scrollY = options.scrollY; - amplitude.getInstance().logEvent("NAVIGATION", { destination: url }); - dispatch({ type: types.HISTORY_NAVIGATE, data: { url, index: options.index, scrollY }, -- 2.45.3 From a9863b90820930f0b8aaffbdf4ef294397efb6b3 Mon Sep 17 00:00:00 2001 From: Liam Cardenas Date: Mon, 18 Dec 2017 22:34:03 -0800 Subject: [PATCH 7/7] Improve click analytics --- src/renderer/component/header/view.jsx | 1 + src/renderer/index.js | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/src/renderer/component/header/view.jsx b/src/renderer/component/header/view.jsx index 1e83abbe7..b3b6cdc51 100644 --- a/src/renderer/component/header/view.jsx +++ b/src/renderer/component/header/view.jsx @@ -46,6 +46,7 @@ export const Header = props => { onClick={() => navigate("/subscriptions")} button="alt button--flat" icon="icon-at" + title={__("My Subscriptions")} />
diff --git a/src/renderer/index.js b/src/renderer/index.js index d5154b084..e3ed7836b 100644 --- a/src/renderer/index.js +++ b/src/renderer/index.js @@ -73,7 +73,8 @@ document.addEventListener("click", event => { if (target.matches("a") || target.matches("button")) { // TODO: Look into using accessiblity labels (this would also make the app more accessible) let hrefParts = window.location.href.split("#"); - let element = target.title || (target.text && target.text.trim()); + let element = + target.title || (target.textContent && target.textContent.trim()); if (element) { amplitude.getInstance().logEvent("CLICK", { target: element, @@ -84,6 +85,7 @@ document.addEventListener("click", event => { amplitude.getInstance().logEvent("UNMARKED_CLICK", { location: hrefParts.length > 1 ? hrefParts[hrefParts.length - 1] : "/", + source: target.outerHTML, }); } } -- 2.45.3