WjValueAccessor Parameters Warning

WjValueAccessor Parameters Warning

Posted by: tfink on 14 September 2017, 12:10 pm EST

• 

  tfink

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:10 pm EST

  Running “ng build --prod” on my Angular project shows this warning from Wijmo

  Warning: Can’t resolve all parameters for WjValueAccessor in C:/Log/wijmo-test/node_modules/wijmo/wijmo.angular2.directiveBase.d.ts: (?). This will become an error in Angular v5.x

  This can be reproduced using the latest version of Wijmo 5 (5.20172.328) and Angular CLI 1.2.1. The steps are:

  1. Extract Wijmo 5.20172.328 to the C:\wijmo folder.
  2. ng new wijmo-test
  3. cd wijmo-test
  4. xcopy C:\wijmo\NpmImages\wijmo-amd-min wijmo\wijmo-amd-min*.*
  5. xcopy C:\wijmo\Dist\styles\wijmo.min.css src\assets*.*
  6. Update package.json dependencies to include “wijmo”: “./wijmo/wijmo-amd-min”,
  7. Update angular-cli.json styles to include “assets/wijmo.min.css”
  8. Add WjGridModule import to the top of app.module.ts.
     
     import { WjGridModule } from “wijmo/wijmo.angular2.grid”;
  9. Add WjGridModule to imports section of the NgModule in app.module.ts.
  10. Add flex grid to bottom of app.component.html
      
      <wj-flex-grid></wj-flex-grid>
  11. npm install
  12. ng build --prod

  I have also attached a copy of this sample project with the node_modules folder.
  
  2017/07/wijmo-test.zip

• 

  tfink

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:10 pm EST

  The last line of the initial message should say “without the node_modules folder.”

• 

  manish-gupta1

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:10 pm EST

  Hi,
  
  We are sorry, we are unable to replicate the issue at our end with build 5.201712.328 and the sample provided by you.

  Steps to Replicate :
  
  Download sample
  
  Extract sample
  
  Navigate to package.json location
  
  Install packages
  
  Run npm build -prod
  
  <Observation> No error/warning found

  Please let me know if there is any missing steps.

  Thanks,
  
  Manish Kumar Gupta

• 

  tfink

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:10 pm EST

  Please try the build using ng instead of npm. This uses the Angular CLI to build the project.

  The build command is

  ng build --prod

  .

• 

  manish-gupta1

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:10 pm EST

  Hello,
  
  We are sorry for the mistake in the previous attempt.
  
  Since this warning id related to Angular version, this issue will be resolved when Angular 5 support will be added. We have escalated this issue to the concerned team for further investigation with tracking id 275177.
  
  We will let you know as soon as we get any information on this.

  Thanks,
  
  Manish Kumar Gupta

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 20 January 2018, 7:51 am EST

  Hi,

  We are sorry for the late.
  
  #275155
  
  We may verified this issue as fixed with build 5.20173.403.

  ~Manish