See my articles on language features and migrating to V8. The legacy Apps Script environment still works too, but we dont know for how long. It fully supports ES6, with the exception of modules, and although Promises are supported syntactically, Apps Script remains synchronous. Previously it ran on an emulator (Rhino – see my analysis here ). nowĪpps Script now runs under JavaScript V8 – the same engine used by Chrome and Node.js. As a baseline it uses JavaScript 1.6, but it also contains features that were implemented in JavaScript 1.7 and 1.8-which we will use heavily in the examples later on. I won’t go into detail about the additions to existing services (for example new methods) as that’s what the Apps Script release notes are for, but rather go into more of the structural or significant changes.ĥ More like this Chapter 1 – Introduction Versions thenĪpps Script is based on the ECMAScript version 3 specification, and is not directly equivalent to any one version of JavaScript in terms of features. This will be series of posts, so this, the first will cover Chapters 1-4 which are the general introduction to the environment and language. How this has changed over the past 5 years I don’t think I have the energy to do a rewrite – so I’m going to do a critique, chapter by chapter, of where it’s now wrong as a way to show how much Apps Script has improved (or otherewise) over the years.Ī summary of or a direct quote from my 2016 book, Going Gas ![]() ![]() It’s been over 5 years since my book ‘ Going Gas‘ was published, and Apps Script evolution means that a number of sections of it is now pretty out of date. This year I thought I’d do something different. I’ve been doing an annual update called ‘a year in Apps Script’ for a number of years now, but I didn’t get round to the 2021 post.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |