-
1. Re: Is it recommended to hot link to the Tableau JS API in production?
diego.medrano Feb 14, 2017 4:10 PM (in response to Charles Chan)1 of 1 people found this helpfulHey Charles,
I'd recommend hosting your own javascript API file only because when we release newer versions, it gives you a chance to test them and make sure they're ready for production before making the links live.
-Diego
-
2. Re: Is it recommended to hot link to the Tableau JS API in production?
Ben LowerFeb 16, 2017 3:47 PM (in response to Charles Chan)
Diego has a valid argument. However you may want to consider just linking to the tableau-2.js or tableau-2.min.js file that we host at public.tableau.com or online.tableau.com because that means that you will always get the latest updates we make to the JS API along the way.
You might be thinking, "But wait. doesn't that mean that things could break?" It's software so yes, something always *could* break
However, we use semantic versioning (http://semver.org/) so you can be assured that we are either only going to make bug fixes or add new features that are non-breaking to your existing code.
If you want to have extreme control, then link to tableau-2.1.2.min.js (or whatever the latest version is on your server). If you want to have the latest bug and perf fixes along with new, non-breaking features, then link to tableau-2.min.js.
Ben