Global Directory
Global Directory
EXPLORE OUR SITES
London Stock Exchange Group
LSEG Data & Analytics
MyAccount
LSEG Perspectives
London Stock Exchange
FTSE Russell
LCH
Contact Us
Home
TR Internal
Route & Debug Product Specific Related Info Static Content
Kyle Reich
How would I go about debugging RI Static Content? I've routed both JS entries in the routing page to my local machine as normal. However, whenever I look at the Source tab in Chrome Dev Tools, none of the product-specific RI files are present (the platform RI files do appear). What am I missing?
As a follow-up, I've added a new product-specific file. With Alerts or Search, I'd add that new file to the Common.js file to make sure it's included. Once again, RI seems to be different because this isn't working (as far as I know since I can't see any product RI files to begin with...).
Find more posts tagged with
static-data
refinitiv-internal
Accepted answers
All comments
Joel Peterson
Kyle,
Not every script file that gets loaded appears in the source tab for Chrome's dev tools. A small set of core files are loaded directly into the page with tags, but then all of the other scripts are pulled in via AJAX and eval'd, which seems to mess with Chrome's dev tools. I would suggest looking at the network tab to see if either the common file or your new file is getting pulled in.
To debug these files, if you add a debugger; statement into your new file, Chrome will automatically break when it hits that as long as you have dev tools open. Just make sure not to check that line in though since it will break the build.
Quick Links
All Forums
Recent Questions
Terms of use
Privacy & Cookie Statement
Cookies settings
Do not sell my info
Whistleblowing
UK Bribery Act
Modern Slavery Act