-
Notifications
You must be signed in to change notification settings - Fork 33
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
Feature/adaptations gpf #364
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… exemples attribution
Dans le fichier AutoLoadConfig.js, on force le mode synchrone pour getConfig() var options = {
apiKey : key,
sync : true,
onSuccess : success,
onFailure : error
};
(...)
Gp.Services.getConfig(options); On ajoute le hack suivant dans le fichier index.js export const Config = (window.Gp) ? window.Gp.Config : {}; |
Les exemples sont à corriger quand on utilise directement Gp.Services.getConfig() afin d'éviter un double appel de l'autoconf : <!DOCTYPE html>
<html>
<head>
<meta content="IE=edge,chrome=1" http-equiv="X-UA-Compatible">
<meta charset="UTF-8">
<link rel="stylesheet" href="../../../dist/openlayers/GpPluginOpenLayers-map.css" />
<script src="../../resources/vendor/ol/v6.9.0/ol.js"></script>
<!-- HERE : 1ER APPEL DE GETCONFIG() -->
<script src="../../../dist/openlayers/GpPluginOpenLayers-map.js" data-key="ortho,cartes,administratif"></script>
<title>Sample openlayers - multikeys</title>
<style>
div#map {
width: 100%;
height: 500px;
}
</style>
</head>
<body>
<div id="map"></div>
<script type="text/javascript">
var createMap = function () { };
<!-- HERE : 2EME APPEL DE GETCONFIG() -->
Gp.Services.getConfig({
// callbackSuffix : '',
apiKey: "essentiels,cartes,adresse,lambert93",
timeOut: 20000,
onSuccess: createMap
});
</script>
</body>
</html> |
…ès aux ressources -> clé calcul par défaut
… des couches GP Pour les 3 librairies - title - description - metadata - legends - quicklookUrl
azarz
approved these changes
May 22, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fonctionnellement OK
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull request checklist
Verifiez que votre Pull Request remplit les conditions suivantes :
npm run build
) a été lancé localement et s'est correctement déroulénpm run samples
) ont été testés et validés localementnpm run test
) sont passés localementType de Pull request
Quel type de changement cette Pull Request introduit-elle :
Quel est le comportement actuel (avant PR) :
L'autoconfiguration est utilisée pour l'ajout simplifié des couches et pour la vérification des droits d'accès aux services utilisés par les différents controles (alti, geocodage, iti...)
Quel est le nouveau comportement :
Cette PR a pour but de se passer du service d'autoconfiguration via l'utilisation de la bibliothèque d'accès aux services sans autoconfiguration.
Chargement synchrone de la configuration. Mise à jour de la documentation.
Plus de vérification des droits d'accès.
Cette PR introduit-elle des breaking changes ?