Book Image

SharePoint Development with the SharePoint Framework

By : Jussi Roine, Olli Jääskeläinen
Book Image

SharePoint Development with the SharePoint Framework

By: Jussi Roine, Olli Jääskeläinen

Overview of this book

SharePoint is one of Microsoft's best known web platforms. A loyal audience of developers, IT Pros and power users use it to build line of business solutions. The SharePoint Framework (SPFx) is a great new option for developing SharePoint solutions. Many developers are creating full-trust based solutions or add-in solutions, while also figuring out where and how SPFx fits in the big picture. This book shows you how design, build, deploy and manage SPFx based solutions for SharePoint Online and SharePoint 2016. The book starts by getting you familiar with the basic capabilities of SPFx. After that, we will walk through the tool-chain on how to best create production-ready solutions that can be easily deployed manually or fully automated throughout your target Office 365 tenants. We describe how to configure and use Visual Studio Code, the de facto development environment for SPFx-based solutions. Next, we provide guidance and a solid approach to packaging and deploying your code. We also present a straightforward approach to troubleshooting and debugging your code an environment where business applications run on the client side instead of the server side.
Table of Contents (14 chapters)

Requesting the list of lists with SPHttpClient

First, ensure that the SPHttpClient is imported in the web part file.

import { SPHttpClient } from '@microsoft/sp-http'; 

Then we need a data model of the list of lists, and we do this by adding a file, ISPList.ts, with the following content. As you can see, we are interested in the Title and Id of the list, but also we are going to retrieve a piece of information about the last change in list items and the nice image URL for the list.

export interface ISPList { 
    Title: string; 
    Id: string; 
    LastItemUserModifiedDate: string; 
    ImageUrl: string; 
} 

To be totally honest, we don't need the data model. We could simply use the raw JSON data that is returned from the GET request. But by using the data model, our code becomes a great deal more readable and our natural ability to create bugs is reduced by the strong typing. In case our data model includes a property that is not returned by the request, its value will...