Skip to content
Branch: master
Find file History
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
assets Replaced the Angular ToDo sample (#152) Mar 12, 2017
config Replaced the Angular ToDo sample (#152) Mar 12, 2017
src/webparts/toDo
typings Replaced the Angular ToDo sample (#152) Mar 12, 2017
.editorconfig Replaced the Angular ToDo sample (#152) Mar 12, 2017
.gitattributes Replaced the Angular ToDo sample (#152) Mar 12, 2017
.gitignore Replaced the Angular ToDo sample (#152) Mar 12, 2017
.npmignore Replaced the Angular ToDo sample (#152) Mar 12, 2017
.yo-rc.json Replaced the Angular ToDo sample (#152) Mar 12, 2017
README.md
gulpfile.js Replaced the Angular ToDo sample (#152) Mar 12, 2017
package.json Replaced the Angular ToDo sample (#152) Mar 12, 2017
tsconfig.json Replaced the Angular ToDo sample (#152) Mar 12, 2017
tslint.json Add tslint at the root of each SPFx project (#394) Jan 8, 2018

README.md

Angular client-side web part

Summary

Sample Web Part illustrating using Angular with the SharePoint Framework.

Sample To do SharePoint Framework client-side web part built using Angular

Used SharePoint Framework Version

drop

Applies to

Solution

Solution Author(s)
angular-todo Waldek Mastykarz (MVP, Rencore, @waldekm)

Version history

Version Date Comments
1.0 March 10, 2017 Initial release

Disclaimer

THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.


Minimal Path to Awesome

  • clone this repo
  • in the command line run:
    • npm i
    • gulp serve

Features

The To do web part is a sample client-side web part built on the SharePoint Framework built using Angular.

This web part illustrates the following concepts on top of the SharePoint Framework:

  • using Angular v1.x with TypeScript for building SharePoint Framework client-side web parts
  • loading Angular from CDN
  • using Office UI Fabric CSS styles in a SharePoint Framework client-side web part
  • using non-reactive web part property pane
  • using conditional rendering for one-time web part setup
  • passing web part configuration to Angular and reacting to configuration changes

You can’t perform that action at this time.