3 ms·
Thanks or the feedback. Regarding manual or tutorial, I agree that its difficult to manage the fields. I namespace the fields into profile, income statement, b
by bko 6y ago
Thanks or the feedback.
Regarding manual or tutorial, I agree that its difficult to manage the fields. I namespace the fields into profile, income statement, balance sheet and quotes so ideally you only have to search [incomeStatement...] and see some fields. But I'll try to list them all out.
Regarding the enums, I thought about that before and wanted to implement auto-complete enums in the language grammar but so it was bit complicated so I decided to kick the can, but I'll circle back around to it. There are only a few string fields and I put in regex matching so you can just do contains `contains "electric"`
What queries didn't return? It's a static site, it shouldn't be affected by the traffic.
The historical data is tough because reporting periods aren't all the same. I don't have a back tester either. I did have a feature before where you can plot any attribute historically, but I didn't find it that useful.
- nilram 6y agoI didn't realize it was running locally, so I think I was inadvertently thrashing it: running in Chrome with many, many tabs open; on an old machine that was probably running low on memory; and randomly pressing F5 instead of Cmd-Enter (some part of my brain was thinking of a SQL environment I use). I added price and industry to the default display, used NYSE and Nasdaq data sets, and queried something like filter profile.lastDiv > 3 and profile.industry startsWith "Utilities" and profile.industry contains "Electric". I probably tried to start my query before the data sets completed loading. I don't know if interrupting the data loading or pressing F5 is more correlated with it acting strangely. (This is on the latest Chrome, under OSX 10.13.6.) I tried again using Firefox 79.0 and it works fine. F5 reloads the page (and logs me out, ahem). Tried to do a few things while it was loading data and it was more solid. I'd put saving column layouts (at least the last one used) ahead of enums for field matching. Seems like once you add enums, you'll have to be continually vigilant for data oddities. I think I'd find it interesting to be able to plot attributes or computed attributes against another. Not sure how other tools get around the reporting period issue. Interesting tool; thanks for putting it out.