Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
en-us.json Documentation

Good Morning,

Is it possible to get documentation related to the translation JSON files used by tecton extensions loaded into the widget fences of the landing page. We are getting 404 errors when these widgets load and can't seem to figure out a way to stub out a file in the correct location to avoid the errors.

If we have no way to prevent these 404s, is it possible to get further insight into why the system is looking for this file and why we can't provide it through the SDK? We would like to avoid any auditing and/or testing confusion on on our institution's end in the future by cleaning up as many errors as possible. Thank you for any insight that you can provide.

2021-06-29 15_07_41-Window.png

Posted 5 years ago
Votes Newest

Answers 2


Thank you Clay. I think that I have found the issue based on your comment. There are technically two extensions at play here because of the widget fence and one had the localization file while the other does not. I think that is the issue.

Posted 5 years ago

Do you have the following internationalization file?

<YOUR_EXTENSION>/frontend/public/assets/resources/en-us_tectonWidget_account_card_dashboard.json

or

<YOUR_EXTENSION>/frontend/public/assets/languages/en-US.json

It should be fine if it's an empty object {}.

Clay Risser

Nueve Solutions LLC

https://nuevesolutions.com