Ember CLI 默认将分析信息发送给谁? [英] Ember CLI sends analytics information by default to who?

问题描述

这是 .ember-cli 文件.

This is the .ember-cli file.

{
  /**
    Ember CLI sends analytics information by default. The data is completely
    anonymous, but there are times when you might want to disable this behavior.

    Setting `disableAnalytics` to true will prevent any data from being sent.
  */
  "disableAnalytics": false
}

默认情况下，Ember CLI 将分析发送给谁?

Who does Ember CLI send analytics to by default?

推荐答案

当我们的工具有开源时，我们可以跟踪任何东西，这不是很神奇吗?让我们一起追踪.

Isn't it amazing that we can track anything in our tools when it has open sources? Let's track together.

问题:一般是什么?

答案:分析工具是leek，用于GA 跟踪.显然它需要一个跟踪代码，所以我们可以看到 它被填充的地方.代码在这里.

The answer: the analytic tool is leek, which is made for GA tracking. Obviously it requires a tracking code, so we can see where it is populated. The very code is here.

问题:它跟踪什么?

答案:我不知道每个跟踪库，但我们可以在存储库中找到一些有用的东西.有 3 个跟踪命令 - trackEvent、trackError 和 track.后来我又找到了一个——trackTiming.

The answer: I don't know every tracking library, but we can find something useful in a repo. There are 3 tracking commands - trackEvent, trackError, and track. Later I found one more - trackTiming.

让我们使用本地 Github 搜索来了解它在 ember-cli 项目中是如何使用的..trackEvent 什么都没有；与 .trackError 唯一相关的 - 发送错误信息.但是一般的 .track 使用得更频繁——我不得不在搜索中使用限制参数.所以最后的事件列表 - 添加/更改文件，构建/重建时间，实时重新加载事件，以及一些 这里不明显.

Let's use native Github search in order to know, how it is used in ember-cli project. Nothing for .trackEvent; the only positive relevant for .trackError - sending an error message. But a general .track is used more frequent - I had to use a limiting parameter in the search. So the final list of events - addition/changing of file, building/rebuilding time, live reloading event, and something not obvious here.

问题:我刚才问谁是收件人，为什么不能直接回答?

The question: I just asked who is a recipient, why can't you answer directly?

答案:现在我们知道，这里的主要参与者是韭菜，所以让我们来看看.该库非常小，因此我们甚至可以对其进行暴力破解.主文件有唯一重要的方法，在这里我们可以很容易的看到网址来源.模块在同一个文件夹中，不幸的是我们的旅程结束这里.

The answer: now we know, that the main player here is leek, so let's go through it. The library is very small, hence we could even bruteforce it. The main file has the only important method, where we can easily see the source of url. The module is in the same folder, and unfortunately our journey ends here.

这篇关于Ember CLI 默认将分析信息发送给谁?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！