Specs

• Leon version: latest
• OS (or browser) version: Fedora 30
• Node.js version: 10.16.3
• Complete "npm run check" output:

➡ Here is the diagnosis about your current setup
✔ Run
✔ Run modules
✔ Reply you by texting
❗ Amazon Polly text-to-speech
❗ Google Cloud text-to-speech
❗ Watson text-to-speech
❗ Offline text-to-speech
❗ Google Cloud speech-to-text
❗ Watson spee

Description

Records are a new primitives in Javascript, and they are currently being implemented in Firefox (See https://bugzilla.mozilla.org/show_bug.cgi?id=1658309, https://bugzilla.mozilla.org/show_bug.cgi?id=1774360 and https://github.com/tc39/proposal-record-tuple)

Records are instantiated like objects, but with a hash before the curly bracket, e.g. #{ hello: "world" }

Input

T

https://github.com/brendangregg/FlameGraph

We can get the response, but that API call only returns metadata, the /details endpoint that returns actual answer data is not available.

Ref: https://developer.surveymonkey.com/api/v3/#api-endpoints-get-surveys-survey_id-responses-response_id-details

Describe the bug
The strings for the Topics values in the UI does not appear to be translated.

To Reproduce
Steps to reproduce the behavior:

1. Go to any dataset or investigation:
2. Create an entity - Person or Company
3. Add a topic property to the entity
4. Go to the dataset search page
5. Filter by Topics and you'll see that the values are not translated.

**Expected behavi