Batch.Execute Returns a Promise
When we introduced batching it was written such that all of your promises would resolve as expected once you called the execute method on the batch. There was however no way to know once all of those promises had resolved. This was addressed by adding support for returning a promise from the execute method which will resolve after all of the individual request promises resolve. This allows you to update the UI, make additional requests, or possibly reset a refresh timer. If you don't need this promise the calling pattern is unchanged so this is non-breaking.
Simplified Getting Fields
We added a method to make it easier to get fields by either internal name or title. This simplifies getting a field and allows for greater flexibility using the getByInternalNameOrTitle method.
Bug Fixes & Improvements
We also added a lot of great fixes and improvements to the library - thanks to everyone from the community that contributed these updates!
- Fixed some file casing issues causing issues in Ubuntu
- Updates to the request executor implementation
- Updates to the documentation
- Updated the version of tslint and gulp-header
- Fixed an issue impacting SharePoint Framework package with webpack
- Updates to clear tslint errors and improve the bithound score
What is the JS Core Component?
“Sharing is Caring”