Hello everyone, I have a problem when I'm trying to navigate in the document list while using a mobile. When I click on a document, instead of openning the overlay to display the document, the document list navigates "inside" the document and displays the doclib and pdf file, screen below :
Anyone already had this behaviour?
@eromano@DenysVuika I upgraded to 3.8.0 for the fix for ADF-5106 and now none of our widgets work? Diidd I need to do anything else to upgrade than change versions from 3.7 --> 3.8
getting Unknown type: <our custom type name>
@tdonovancsra - we're seeing the exact same thing. Did nothing but upgrade and the widget broke. Seems like maybe the formRenderingService.setComponentTypeResolver isn't working.
What is the new behaviour?
new ProcessFormRenderingService (alfresco/process-services)
new CloudFormRenderingService (alfresco/process-services-cloud)
@DenysVuika I'm trying any combination of injecting ProcessFormRenderingService into my component - with no luck so far. I noticed typeId was added to the custom widgets which extend WidgetComponent - so I added that. I've even tried making a custom form rendering service which extends ProcessFormRenderingService and no luck so far. I just cannot get it to recognize my custom widget. It always says Unknown type in the form.
It feels like form.component.ts is now running off of its own instance of ProcessFormRenderingService, which I don't have access to in my component and can't register my custom widget with.
All this code works on 3.6 and 3.7 and just follows the examples in demo-shell and the yo generator. I assume those don't work with 3.8.
The typeId was added to our widgets just to facilitate unit testing, it has no value outside our test suits
You can refer to the whole suit of unit tests to see what was changed: https://github.com/Alfresco/alfresco-ng2-components/pull/5601/files. I don't know how your code looks like, but you should not be redefining any custom classes, or replacing the FormRenderingService with anything else. It's hard to say why your code is failing without any steps to reproduce, but check out the unit tests we have