Skip to content

Update to be compatible with Maplibre everywhere #74

@aparlato

Description

@aparlato

The "Style was not found error" is pretty generic right now and will kind of report that for any issue that happens when fetching (which includes various validation and other checks and transforms).

Use of later Maplibre expressions after it diverged from Mapbox can cause this issue due to a couple of Maplibre/Mapbox mismatches among other related issues.

We need to:

  • update Mapbox and Maplibre packages to the latest versions to allow for new expressions that don't throw
  • make sure we've updated versions of packages that use Maplibre/Mapbox (eg mapbox-expression)
  • make sure everywhere we validate or otherwise use the style spec accounts for both libraries as possibilities
  • get around Mapbox specific packages we rely on to parse expressions and/or gracefully fail and skip layers

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions