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

Move plugins configuration from initConfig to project config #372

Closed
volterra79 opened this issue Sep 7, 2022 · 1 comment · Fixed by #836
Closed

Move plugins configuration from initConfig to project config #372

volterra79 opened this issue Sep 7, 2022 · 1 comment · Fixed by #836
Labels
refactoring Anything which could result in a API change

Comments

@volterra79
Copy link
Member

It could be better move plugin configuration from:
initConfig = { ... group: { plugins: { editing: {....}, .... } }
to project config

{ id: 1, name: 'Project 1', ..., plugins: { editing: {....} } }

maybe after #371

@volterra79 volterra79 added feature New feature or request refactoring Anything which could result in a API change labels Sep 7, 2022
@Raruto Raruto removed the feature New feature or request label Sep 15, 2022
@wlorenzetti
Copy link
Member

@Raruto @volterra79 this is a very big refactoring issue!! :(

Raruto added a commit that referenced this issue May 3, 2024
Raruto added a commit that referenced this issue May 6, 2024
…up` property (#836)

* Ensure absolute URL for `initConfig.baseurl`

* fallback to absolute URL

* slim down `ClientView` response

* tests

* closes: #372

* tests

* tests

* g3w-suite/g3w-client@ecc1cb2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Anything which could result in a API change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants