I had some issues with the translations showing up at the 17:00 ish mark I had to add code that setupmessages for spanish and say chinese, and then a method that would get the query paremters for loacle and then use that to return through a constant in render for localeMessages (rather than defaultMessages) once I did that it worked. I think this can be done globaly, but its interesting to do it just for a widget.
It seems that on Experience Builder 1.4, JimuMapViewComponent needs to be passed the prop 'useMapWidgetId': string, instead of 'useMapWidgetIds' :string[], so the whole component looks like:
I had some issues with the translations showing up at the 17:00 ish mark I had to add code that setupmessages for spanish and say chinese, and then a method that would get the query paremters for loacle and then use that to return through a constant in render for localeMessages (rather than defaultMessages) once I did that it worked. I think this can be done globaly, but its interesting to do it just for a widget.
Could one work simultaneously with the developer edition of experience builder and the drag and drop version? they are synced?
It seems that on Experience Builder 1.4, JimuMapViewComponent needs to be passed the prop 'useMapWidgetId': string, instead of 'useMapWidgetIds' :string[], so the whole component looks like: