Topic: NO_ERRORS_SCHEMA
NO_ERRORS_SCHEMA is not recommended generally, but is required for some MDB components to run. Why is this? What is the purpose of NO_ERRORS_SCHEMA? (and when is it best practice to use?).
Can use of NO_ERRORS_SCHEMA be avoided?
Thanks.
As you know angular is quite new product and it's still taking its shape. We were making quite a lot of updates and we will slowly progress to make it without such issues. Thanks for writing about this. Every constructive comment has a huge value for us.
Closed
This topic is closed.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Status
Closed
Specification of the issue
- User: Pro
- Premium support: No
- Technology: MDB Angular
- MDB Version: -
- Device: -
- Browser: -
- OS: -
- Provided sample code: No
- Provided link: No
Bldg25 pro commented 7 years ago
Followup: It is my opinion that if you think you should use NO_ERRORS_SCHEMA outside unit testing then you should re-examine what is causing the requirement. In the case of NavbarComponent the template uses the element "links" but there is no component defined. Perhaps there is a future plan to create a link component and logo component, but for now perhaps set the select to ".links" so that NO_ERRORS_SCHEMA is not required. I am free to change your code myself, however this is a poor choice in the face of future updates on the component set.