Skip to content
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

Add extension variables and parameters #87

Open
guillett opened this issue May 29, 2017 · 2 comments
Open

Add extension variables and parameters #87

guillett opened this issue May 29, 2017 · 2 comments

Comments

@guillett
Copy link
Member

No description provided.

@MattiSG
Copy link
Member

MattiSG commented May 31, 2017

This one is not obvious: which extensions should be loaded? Maybe it is up to each extension vendor to set up their own instance of the legislation explorer.

@guillett could you please provide us with some more insight into your use case? Which extensions would you need, and why is their documentation not sufficient?

@Morendil
Copy link
Contributor

Yes, for instance https://fr.openfisca.org/legislation/ makes sense as "the explorer for France" but it's harder to infer from the subdomain a canonical set of extensions that it should be loading.

It would make sense (for instance) for Mes Aides to have access to an explorer instance that eases debugging for the situations computed on behalf of Mes Aides users. It might be a good idea to make this a test bed for #143, reframing the definition of the goal as "Help Mes Aides host an instance of the Legislation Explorer that shows variable from all extensions configured to be loaded". Possibly at https://mes-aides.gouv.fr/legislation/ See what's involved in doing that, and smooth over the more significant frictions we find.

@guillett WDYT ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants