Patrick Rodgers

PnP JSCore 3.0.4 (sp-pnp-js@3.0.4)

Patrick Rodgers (MSFT) — Mon, 15 Jan 2018 11:53:49 GMT

This month’s release of sp-pnp-js, 3.0.4, brings some great new functionality as well as fixes for reported issues. Give it a try and as always let us know if you see any issues. Be sure to check out the developer guide and happy coding!

New Features

Adds support for navigation service [PR] [Issue] [Docs]
Adds allproperties shortcut to Web object [PR] [Issue]
Adds Refiners collection to ResultTable interface [PR]
Adds support to send attachment files to recycle bin [PR]
Makes public a static method to parse batch responses [PR] [Issue/Discussion]

Fixes & Updates

Fixes an issue with RenderListData in verbose mode [PR] [Issue]
Fix for a change in BasePermissions to have string properties [PR] [Issue]
Remove NavigationNode update method as it does nothing on server [PR] [Issue]

What is the JS Core Component?

The Patterns and Practices JavaScript Core Library was created to help developers by simplifying common operations within SharePoint and the SharePoint Framework. Currently it contains a fluent API for working with the full SharePoint REST API as well as utility and helper functions. This takes the guess work out of creating REST requests, letting developers focus on the what and less on the how. “Sharing is Caring”

PnP JSCore 3.0.3 (sp-pnp-js@3.0.3)

Patrick Rodgers (MSFT) — Mon, 18 Dec 2017 12:27:06 GMT

This month’s release of sp-pnp-js, 3.0.3, brings some great new functionality as well as fixes for reported issues. Give it a try and as always let us know if you see any issues. Be sure to check out the developer guide and happy coding!

New Features

Add ability to get list item version information [PR] [Issue]
Adds support for web/EffectiveBasePermissions endpoint implementation [PR] [Issue]
Adds support for regional settings [PR, PR2] [Issue]

Fixes & Updates

Fixes typing issue for getPropertiesFor [PR] [Issue]
Fix a comment typo

What is the JS Core Component?

PnP JSCore 3.0.2 (sp-pnp-js@3.0.2)

Patrick Rodgers (MSFT) — Tue, 28 Nov 2017 12:07:23 GMT

This month’s release of sp-pnp-js, 3.0.2, brings some great new functionality as well as fixes for reported issues. Give it a try and as always let us know if you see any issues. Be sure to check out the developer guide and happy coding!

New Maintainer!

I am very happy to announce that Andrew Koltyakov will have a larger role in helping to maintain the library moving forward. He has been active helping folks with issues and on gitter - as well as submitting PRs and fixing bugs. Very much appreciated all his help and initiative in getting involved, especially while I was one leave. He will be assisting with merging PRs in addition to helping folks out. Congratulations to Andrew on the great work!

New Features

Support for SharePoint ALM apis [PR] [Docs]
Add support to delete multiple attachments [PR] [Docs]
Add support for GetStorageEntity endpoint [PR]
Adds capability of getting external lists items by "getItemByStringId" [PR]
Add support for SiteUserInfoList endpoint [PR]

Fixes & Updates

Fixed an issue with getAs and caching not rehydrating objects from cache [PR] [Issue]
Cleaned up utilities class to use shared clone method [PR]
Updates to Authors file

What is the JS Core Component?

What's going on with Patrick?

Patrick Rodgers (MSFT) — Mon, 13 Nov 2017 20:06:06 GMT

Wanted to put out a short post to update the community on why I've been absent and plans for the future. Long story short we've got great things coming up for Patterns and Practices client side development! First, on a personal note I've been on family leave spending time with my new son. It has been a fantastic opportunity and I am very thankful to Microsoft for allowing me this time. And that's why I haven't been as responsive as usual or put out a new release recently. But it is almost time to get back to work - so wanted to provide everyone a very rough outline of what is upcoming since I've been radio silent. Second, here is a short list of what is upcoming:

When I get back I'll be reviewing the issues list and merged PRs and cutting a release pretty quickly. That will be 3.0.2 of sp-pnp-js. Expect that by the end of November.
Next I'll be working on docs for the new libraries which are a dependency for our first release (won't go live without at least basic docs). Aim is to have the new work out by the end of the year.
And finally we'll begin transferring development efforts to the new library for future updates. We are committed to maintaining the existing library (sp-pnp-js) for 6 months but that will consist of bug fixes only. Don't stress about this yet, we'll have more details as well as a detailed transition guide available when appropriate. We will of course continue to accept PRs from folks wishing to make contributions to sp-pnp-js.

So that's it - but wanted to let folks know where I've been and what we have upcoming. Hope everyone had a good few months and look forward to reengaging with everyone in the SharePoint development community. Cheers!

PnP JSCore 3.0.1 (sp-pnp-js@3.0.1)

Patrick Rodgers (MSFT) — Wed, 20 Sep 2017 14:34:36 GMT

We are pushing a quick release of the sp-pnp-js library to 3.0.1 to address two blocking issues for folks. Apologies for the issues and any disruption this caused - please keep giving us the excellent feedback so we can resolve things like this quickly. Would ask that you please upgrade any 3.0.0 installations to avoid these issues.

New Features

Support for /_api/web/getsubwebsfilteredforcurrentuser [Issue] [PR]

Fixes & Updates

Returned the exports to the root. [Issue] [PR]
Added missing dependency in package.json [Issue] [PR]

What is the JS Core Component? The Patterns and Practices JavaScript Core Library was created to help developers by simplifying common operations within SharePoint and the SharePoint Framework. Currently it contains a fluent API for working with the full SharePoint REST API as well as utility and helper functions. This takes the guess work out of creating REST requests, letting developers focus on the what and less on the how. “Sharing is Caring”

PnP JSCore 3.0.0 (sp-pnp-js@3.0.0)

Patrick Rodgers (MSFT) — Fri, 15 Sep 2017 13:12:18 GMT

This month’s release of sp-pnp-js, 3.0.0, marks a big step - this will be the last major release for sp-pnp-js, details below - more and better is coming. Please give it a try and let us know if you see any issues. Be sure to check out the developer guide and happy coding! When moving to this release we recommend reviewing the guide as there has been some restructuring of the library. The core use cases should remain relatively unchanged, but expect to make some changes when moving.

New Features

Graph Support! - Currently with some limitations. Docs and examples coming. Official MS Graph docs
Support for the RenderListDataAsStream method [PR] [Issue]
Performance improvement for updating list items [PR] [Issue] [Example]
Added section on updating file properties after upload
Guide for moving from 2 .0.* to 3.0.*

Fixes & Updates

Chaining .getByLoginName(login).groups loses LoginName parameter [Issue] [PR]
Files API does not work from within add-in webs [Issue] [PR]

What is next for sp-pnp-js?

As I mentioned at the top of the post 3.0.0 will be the final major release for sp-pnp-js. We will continue to patch this release for critical bugs or blocking issues, however new features will no longer be added. Instead we are moving development to a new repo and releasing scoped packages under @pnp. This is a big change, and we understand a disruptive one. But ultimately it is the right thing to do for a number of reasons:

Greater freedom to publish individual packages within the scope
Allows us to expand our coverage beyond SharePoint, without forcing folks to take one huge package
Gives greater flexibility to folks consuming the library to choose the pieces they want to use and extend
Makes the pnp library align with how others large projects are managed (mono-repo, lock-step versioning, scopes, es2015 modules included in package)

There are beta versions of the new libraries published. These are a preview and to provide a way to see where we are heading and get constructive feedback. We do not yet suggest using these in any production code, continue to use the 2.0.* or 3.0.* versions of sp-pnp-js. If you don't need any of the new functionality or bug fixes in 3.0.0, we recommend staying within the 2.0.* stream and then make your upgrade effort to @pnp/*. For any issues you find in sp-pnp-js please continue to report them to the same issues list, and we will be patching bugs so folks aren't stuck. Once we are ready to begin transitioning to the new libraries we'll ensure we have a transition guide, docs, and samples to make things as easy as possible.

Thank You

I wanted to add a big thank you to everyone that uses, supports, and provides feedback on the library. You have made this a success and enabled us to grow to this point. I am excited for what is to come and sharing the journey with you all. And give the new repo a look and a star. Thank you.

What is the JS Core Component?

sp-pnp-js@3.0.0-beta & the road ahead

Patrick Rodgers (MSFT) — Tue, 29 Aug 2017 11:40:43 GMT

sp-pnp-js 3.0.0 beta

Today we are releasing the first beta version of 3.0.0 for sp-pnp-js. This is a breaking change and may require updates to your code. You can see a run down of the changes here, and please remember these changes themselves might change before the final release. Under the hood we have rewritten much of the internals of the library, including the request pipeline and the class inheritance structure. These changes were big, but are our first move down a longer term plan (see below). It is not recommended to upgrade to this beta version for anything going to production as it may change - or simply not work in some way we didn't catch in our testing. Because this is a beta we welcome extra feedback from folks, especially in a few key areas (once you've made any needed updates to your code). You can log an issue in the normal place, but please put "3.0.0-beta" in the title to help us triage.

Any code that was working still works. This is number 1, we can't break folks.
Try out the graph functionality and let us know how things are working
Are all the exports you were using in the global namespace available in the sub namespaces

Known Limitations

There are some known limitations with this beta release, and would ask that you please not log an issue regarding them

Graph requests only work within SPFx and through the GraphHttpClient and are subject to the same scoping limitations. This is not the end state, we understand folks would like to use the library in node and plain javascript applications - that will come.
Global exports are not available in the distributed pnp.js files.
The dist file sizes are getting bigger, see below for our plan to address this
Graph batching is not yet supported

the future

When we started this project I did not anticipate how it would grow in both scale and popularity. This is an amazing and humbling problem to have and I want to thank everyone in the community for the support, contributions, and interest in our work. But it means we need to make some changes. 3.0.0 will be the last major release of sp-pnp-js. We will leave the repo in place and continue to patch critical bugs, but we will be moving new development to a new organization within github and a new repo. As part of this move we will completely restructure the library, breaking things up into smaller packages you can combine as needed. This will take a lot of work - but it is the right thing to do to support our long term goals:

Expand our support of O365 services beyond SharePoint
Provide a mix of packages instead of a single library, allowing folks to use only what they need more easily (and help with size)
Create a smooth transition from sp-pnp-js to the new libraries with clear guidance
Updated docs to reflect the changes

We'll provide more details as we solidify things and make beta versions available ASAP to get feedback early. While we recognize these changes will be disruptive we believe it is the best way to provide the best service possible to you. As always please share your thoughts. Thanks!

PnP JSCore 2.0.8 (sp-pnp-js@2.0.8)

Patrick Rodgers (MSFT) — Wed, 16 Aug 2017 13:55:08 GMT

This month’s release of sp-pnp-js, 2.0.8, brings some great new functionality as well as fixes for reported issues. Give it a try and as always let us know if you see any issues. Be sure to check out the developer guide and happy coding!

New Features

Adding File and Files to the global exports [PR] [Issue]
Added ability to remove expired items from cache [PR] [Issue] [Docs]
New documentation for adding webs

Fixes & Updates

Fix to handle 200 response with empty or whitespace only body [PR] [Issue 1 & 2]
Fixed Incorrect behaviour when using configure with getParent on Queryable [PR] [Issue]
Implemented suggested change in getPage [PR] [Issue]
Updated package.json to latest of all dependencies [PR 1 & 2]

What is the JS Core Component?

PnP JSCore 2.0.7 (sp-pnp-js@2.0.7)

Patrick Rodgers (MSFT) — Tue, 11 Jul 2017 09:37:56 GMT

This month’s release of sp-pnp-js, 2.0.7, brings some great new functionality as well as fixes for reported issues. Give it a try and as always let us know if you see any issues. Be sure to check out the developer guide and happy coding!

New Features

Added configure method for per-request settings [PR][Issue][Docs]
Added a version number to the deprecated decorator [PR]
Updates to support TypeScript 2.4.1 [PR][Issue]
Updated project references & made any associated changes [PR]

Fixes & Updates

Fix for requireSignin parameter in sharing [PR]
Fix header casing issue with batching [PR][Issue]
Fixed issue with date formats in certain time zones [PR][Issue]
Handle verbose odata mode in getUserEffectivePermissions [PR][Issue]
Fixed issue when chaining off the Item returned by getItem [PR][Issue]
Fixing issue with SearchRequest property casing [PR][Issue]

What is the JS Core Component?

PnP JSCore 2.0.6 (sp-pnp-js@2.0.6)

Patrick Rodgers (MSFT) — Tue, 13 Jun 2017 08:54:54 GMT

This month’s release of sp-pnp-js, 2.0.6, brings some great new functionality as well as fixes for reported issues. Give it a try and as always let us know if you see any issues. Be sure to check out the developer guide and happy coding!