-
-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Style spec references code from maplibre-gl #2054
Comments
Once resolved, I'd like to enforce this from happening again by enabling the eslint import/no-relative-packages rule |
The build scripts for style-spec live in the maplibre-gl package. They should probably also be moved within the style spec subpackage. |
Place in style spec which reference maplibre-gl-js code are:
|
Removing |
Wht are these referenced? Moving the style spec to a different repo will also help solving this. |
Ah the references are just the places where file in the |
Some of these circular dependencies were introduced here: mapbox/mapbox-gl-js#9428 and here: mapbox/mapbox-gl-js#9352 |
|
@wipfli, could you fix the refs in |
EXTENT seems to be hardcoded in a bunch of places. |
And the class mercator coordinate defined here:
Might be similar to this point module or how it is called and maybe could be factored out. |
The style-spec actually compiles without importing anything from maplibre-gl-js at this point. This is obtained by having MercatorCoordinate is inside of style-spec here: Only the type of CanonicalTileID is used in style-spec, so there is an interface ICanonicalTileID here, which is imported maplibre-gl-js as well: Also, the LngLat type is necessary for MercatorCoordinate, so it's also to be found in style-spec here: |
The following identifiers are defined in the
maplibre-gl
package but are referenced from the style spec.Their definitions should be moved to the style spec. The code needs to be reorganized to prevent the style spec from being dependent on the implementation:CanonicalTileID
MercatorCoordinate
EXTENT
The text was updated successfully, but these errors were encountered: