Update grafonnet import paths to absolute import paths #139
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Users integrating the dashboards into mixins might use colliding relative import paths.
This might be for example the case for:
https://github.com/grafana/grafonnet
https://github.com/grafana/grafonnet-lib (subdir grafonnet)
Using absolute import paths instead of relative import paths should resolve this collision for dependencies in distinct repositories.
Description
This PR updates the relative import paths
grafonnet/main.libsonnet
to absolute import pathsgithub.com/grafana/grafonnet/gen/grafonnet-v10.4.0/main.libsonnet
to avoid jsonnet import path collisions.