sp-dev-fx-webparts/samples/knockout-taxonomy
Hugo Bernier 810a68ebee Updated contributors for readmes 2023-03-15 00:11:27 -04:00
..
.devcontainer added remaining containers 2022-02-16 21:47:07 -05:00
.vscode Logic implemented 2016-11-11 17:11:56 -08:00
assets Changed docs links to learn 2022-10-24 09:42:45 -04:00
config Knockout taxonomy update (#197) 2017-05-08 21:32:08 +03:00
src Knockout taxonomy update (#197) 2017-05-08 21:32:08 +03:00
typings Knockout taxonomy update (#197) 2017-05-08 21:32:08 +03:00
.editorconfig Logic implemented 2016-11-11 17:11:56 -08:00
.gitattributes Logic implemented 2016-11-11 17:11:56 -08:00
.gitignore Logic implemented 2016-11-11 17:11:56 -08:00
.npmignore Logic implemented 2016-11-11 17:11:56 -08:00
.yo-rc.json Logic implemented 2016-11-11 17:11:56 -08:00
README.md Updated contributors for readmes 2023-03-15 00:11:27 -04:00
gulpfile.js Logic implemented 2016-11-11 17:11:56 -08:00
knockout-metadata.njsproj Logic implemented 2016-11-11 17:11:56 -08:00
package.json Knockout taxonomy update (#197) 2017-05-08 21:32:08 +03:00
tsconfig.json Knockout taxonomy update (#197) 2017-05-08 21:32:08 +03:00
tslint.json Add tslint at the root of each SPFx project (#394) 2018-01-08 15:58:48 +02:00

README.md

page_type products languages extensions
sample
office-sp
javascript
typescript
contentType technologies platforms createdDate
samples
SharePoint Framework
knockout
1/1/2016 12:00:00 AM

Taxonomy

Summary

Sample Web Part illustrating

  • Reading taxonomy term stores' hierarchy from SharePoint
  • Loading JavaScript Object Model scripts
  • creating Knockout components

Taxonomy Sample Web Part

Compatibility

⚠️ Important
Every SPFx version is only compatible with specific version(s) of Node.js. In order to be able to build this sample, please ensure that the version of Node on your workstation matches one of the versions listed in this section. This sample will not work on a different version of Node.
Refer to https://aka.ms/spfx-matrix for more information on SPFx compatibility.

SPFx 1.0.0 Node.js v6 Compatible with SharePoint Online Compatible SharePoint 2019 Compatible with SharePoint 2016 (Feature Pack 2) Local Workbench Compatible Hosted Workbench Compatible Compatible with Remote Containers

Applies to

Contributors

Version history

Version Date Comments
1.0 November 12, 2016 Initial release
1.1 May 5, 2017 Update to GA Release, fix of minor bug

Minimal Path to Awesome

  • Clone this repository
  • in the command line run:
    • npm i
    • gulp serve

This sample can also be opened with VS Code Remote Development. Visit https://aka.ms/spfx-devcontainer for further instructions.

Features

This project contains Client-Side Web Part built on the SharePoint Framework illustrating how to request Taxonomy Term Stores' hierarchy from SharePoint. This Web Part illustrates the following concepts on top of the SharePoint Framework:

  • Reading taxonomy term stores' hierarchy from SharePoint
  • Loading JavaScript Object Model scripts (init.js, sp.runtime.js, sp.js, taxonomy.js)
  • creating custom Knockout components
  • styling HTML elements to match Fabric UI experience

Help

We do not support samples, but this community is always willing to help, and we want to improve these samples. We use GitHub to track issues, which makes it easy for community members to volunteer their time and help resolve issues.

If you're having issues building the solution, please run spfx doctor from within the solution folder to diagnose incompatibility issues with your environment.

You can try looking at issues related to this sample to see if anybody else is having the same issues.

You can also try looking at discussions related to this sample and see what the community is saying.

If you encounter any issues while using this sample, create a new issue.

For questions regarding this sample, create a new question.

Finally, if you have an idea for improvement, make a suggestion.

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.