honeymoose
/
sp-dev-fx-webparts
mirror of https://github.com/pnp/sp-dev-fx-webparts.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Small readme adjustments

This commit is contained in:
Vesa Juvonen 2016-11-04 11:44:19 +02:00
parent 62abc411a0
commit 1275b2ca9a
2 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
samples/angular-search/.vscode/settings.json vendored
View File

@ -18,4 +18,6 @@
"lib": true,
"temp": true
}
,
"typescript.check.workspaceVersion": false
}

7
samples/angular-search/README.md
View File

@ -10,12 +10,9 @@ available through SharePoint's REST API.
The logic for querying the SharePoint Content Types in the properties of the webpart was in part due to Chris O'Brien and this [blog post](http://www.sharepointnutsandbolts.com/2016/09/sharepoint-framework-spfx-web-part-properties-dynamic-dropdown.html?m=0)
> Note: In order to use the ngOfficeFabric code I use the ModuleLoader to load newer source files than the currently
> Office Fabric UI in SharePoint Online, which will cause many of the icons not to load properly on the SharePoint
> Page this webpart is added to.
> Note: In order to use the ngOfficeFabric code I use the ModuleLoader to load newer source files than the currently Office Fabric UI in SharePoint Online, which will cause many of the icons not to load properly on the SharePoint Page this webpart is added to.
> Note: For the display template of the search results I'm currently using the Office Fabric UI List template. Ideally
> I was hoping to use the DocumentCard Component, however, that is not yet available through the ngOfficUIFabric.
> Note: For the display template of the search results I'm currently using the Office Fabric UI List template. Ideally I was hoping to use the DocumentCard Component, however, that is not yet available through the ngOfficUIFabric.
## Applies to