by Luc Saffre · in Developers · assigned to Sharif Mehedi

Summary

Children

Comments

• 5 years, 6 months ago by Luc Saffre about #4104 (Failed prop type: Invalid prop `disabledFields` of type `array` supplied to `LinoBbar`, expected `object`) : Confirmed. Yes, it works now. Cool!
• 5 years, 6 months ago by Luc Saffre about #4104 (Failed prop type: Invalid prop `disabledFields` of type `array` supplied to `LinoBbar`, expected `object`) : Why "sudo" before the "npm install"? Works well without sudo. (on my machine it also said "New minor version of npm available! 7.7.6 -> 7.9.0" and "Run npm install -g npm@7.9.0 to update!", but that's unrelated.)
  
• 5 years, 6 months ago by Sharif Mehedi about #4104 (Failed prop type: Invalid prop `disabledFields` of type `array` supplied to `LinoBbar`, expected `object`) : This was actually introduced by my work. I wrote some explicit submit call to Grid Editor Submit. But there's no such thing where there's no Grid. And I forgot to check for that. Anyway, it is okay to work with now.
• 5 years, 6 months ago by Sharif Mehedi about #4104 (Failed prop type: Invalid prop `disabledFields` of type `array` supplied to `LinoBbar`, expected `object`) : All done. But I could not commit the main.js because of my other unfinished edits, sorry for the inconvenience. Please do the following after cloning on you machine. sudo npm install npm run build (or npm run dev) whichever you prefer
• 5 years, 6 months ago by Luc Saffre about #4104 (Failed prop type: Invalid prop `disabledFields` of type `array` supplied to `LinoBbar`, expected `object`) : This console warning comes (and the browser screen is blank) when I create a comment from the detail window of a ticket in noi1r with the current version.