OpenUI5 version:
1.40.6
Hello,
I tried to get code completion in Visual Studio running, but it seems there are some issues with the xsd files. On sap.m.xsd I get following warning:
'null:DateTypeRange' is an invalid value for the 'ref' attribute.
on the element
in line 7285
When I run the schema check of xml tools in notepad++ I also get errors on each line using null:xyz elements.
Webstorm does not seem to bother and works fine.
Can this be fixed somehow?
Seems that there is a dependency missing from library sap.m to library sap.ui.unified. Therefore the schema generation does not know about the types from sap.ui.unified when building the schema for sap.m (sap.ui.unified.DateTypeRange is the missing type).
I guess if there are more null:xyz references, then it has similar reasons.
As schema generation is not a major delivery, it does not break the build. AFAIK, the dependency from sap.m. to sap.ui.unified is not "wanted" (although it exists).
Let's wait and see what the owners of "sap.m" comment on this.
Hi @apazureck, does the problem still reproduce in VS ?

Works now as it should. Great job!
sap.m still has a problem :(
7697 <xsd:element ref="null:DateTypeRange"/>
7780 <xsd:attribute name="appointmentsVisualization" type="null:_CalendarAppointmentVisualizationType">
7957 <xsd:element ref="null:CalendarAppointment"/>
7877 <xsd:element ref="null:CalendarAppointment"/>
Error Message: type attribute is invalid
I've created a internal incident 1770165828. You can check its status on GitHub.
Hello, sap.ui.unified was added to the .library file as a lazy dependency for sap.m
Regards
Most helpful comment
Seems that there is a dependency missing from library sap.m to library sap.ui.unified. Therefore the schema generation does not know about the types from sap.ui.unified when building the schema for sap.m (sap.ui.unified.DateTypeRange is the missing type).
I guess if there are more null:xyz references, then it has similar reasons.
As schema generation is not a major delivery, it does not break the build. AFAIK, the dependency from sap.m. to sap.ui.unified is not "wanted" (although it exists).
Let's wait and see what the owners of "sap.m" comment on this.