Closed alecmev closed 4 years ago
@orta @DanielRosenwasser Please, take a look, this fixes the most upvoted open issue.
Conceptually this looks good, I need to get a working ST3 dev env again to verify this all works before I can merge - I might have time for that tomorrow 👍
@orta Friendly ping :wink:
Thanks for the ping!
Thank you for dedicating time to this!
We reverted these changes, after looking at it we realized that the constant lookback for the tsdk could be a cross-user code eval security hole ( C:/
is writable for all users on a machine )
We reverted these changes, after looking at it we realized that the constant lookback for the tsdk could be a cross-user code eval security hole (
C:/
is writable for all users on a machine )
What ..?
So how come we'll use the react jsx now, provide help please!!
Fix #538
This is flawed, of course, since the server used is never updated once initialized, so gotta restart ST when switching to/from a project with a custom
typescript_tsdk
set, but I can't afford to spend time on a refactor to accommodate this, and this is still much better than the status quo.