[Oskari-user] Oskari 3.2.0 released!

[Mäkinen Sami]

Good news everyone,

The new version is now available on GitHub (https://github.com/oskariorg) and Oskari.org Maven repository. The sample application package has been updated on the download link in Oskari.org (https://oskari.org/download) and http://download.osgeo.org/oskari/. As always you can take a peek at the latest release at https://demo.oskari.org/.

The release doesn't have many visible changes for end-users, but it does have lots of libraries updated for the frontend like:

  *   React 16 -> 18
  *   Webpack 4 -> 5
  *   ESLint 8 -> 9
  *   Improved developer experience by continuing bundle loader changes what were started on 3.0 (only the jQuery-based ui-components packages remain on the old loader).
  *   Some "always enabled" map related code was packaged as part of the mapmodule to reduce boilerplate code and config.
  *   Other smaller fixes and tunings

Upgrading from 3.1.x requires some/minor code changes for your Oskari-based application (bundle reference/loader changes on main.js). Any application specific React-based bundles will require some changes because of the React-upgrade as well. These are documented on the release notes.

The compiled list of release notes can be found on https://oskari.org/documentation/docs/3.2.0/12-Changelog

Happy updating,
      Sami

PS. There's a preview version of the new "myfeatures" functionality available on the release. At this point it requires some additional configuration to enable the functionality on your application as described on the release notes. The new functionality on 3.2.0 matches what "userlayer" functionality can do today (importing your own datasets to Oskari). I wouldn't recommend this for production yet as it isn't as battle tested as userlayers are, but at the next release it might be even better already. Next steps for the functionality are adding the "myplaces" functionality to "myfeatures" and at some point we will be migrating both "userlayer" and "myplaces" functionalities to "myfeatures" and deprecating the old implementations. We are tinkering with the idea of replacing "userlayer" on the sample-application with "myfeatures" for the next release and we are open for input if we should make a full migration of existing "userlayers" into "myfeatures" and basically deprecating the "userlayer" functionality already at this point. Another option is allowing you to choose which one to use and force the migration later. Anyway, you can consider this replacement a part of the roadmap for future Oskari version. For more information: https://github.com/oskariorg/oskari-docs/issues/31

PPS. We are also developing a new layer listing backend that helps with instances that have a lots of layers on them. The change is building on the fact that listing layers can be done as it is today with much more efficient response from the server. We don't need to know what the default opacity or styles for the layers are when listing them as options for the user to select from. We only need that detailed information when the user actually adds the layer on the map. This is something that is already used to load tile matrix configurations for WMTS-layers etc through the DescribeLayer endpoint/action route. What this means for the frontend is that most of the information about layers would not be available (on MapLayerService) before the user actually adds them to the map. This might very well break things for applications so I'm very interested in hearing your thoughts on this as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/oskari-user/attachments/20251127/618b76e0/attachment.htm>