You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect the deployed version running on a modern page to run as per the local workbench version. I am wondering if this is because the web part site within a larger FORM on the page or some bundling issue.
Observed Behavior
Works in the workbench, but (after renaming the bundle, see: #405, perhaps related) I get the following error:
Unhandled Promise rejection: Template parse errors:
Can't bind to 'ngmodel' since it isn't a known property of 'input'.
Steps to Reproduce
Use SharePoint Yeoman to create a project, create an app folder with angular assets in it, bootstrap load the angular 2 module to the web part. See:
amishra0909
added
the
status:tracked
Currently tracked with Microsoft’s internal issue tracking system. DO NOT ADD/REMOVE (MSFT managed)
label
May 9, 2017
Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues
Category
Expected or Desired Behavior
I would expect the deployed version running on a modern page to run as per the local workbench version. I am wondering if this is because the web part site within a larger FORM on the page or some bundling issue.
Observed Behavior
Works in the workbench, but (after renaming the bundle, see: #405, perhaps related) I get the following error:
Unhandled Promise rejection: Template parse errors:
Can't bind to 'ngmodel' since it isn't a known property of 'input'.
Steps to Reproduce
Use SharePoint Yeoman to create a project, create an app folder with angular assets in it, bootstrap load the angular 2 module to the web part. See:
http://www.sharepointtweaks.com/2016/08/sharepoint-framework-angular2-sample.html
This has the following app.module.ts:
And RequirementsFormWebParts.ts has:
The text was updated successfully, but these errors were encountered: