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

Request GetFeatureInfo with Bootstrap5 #4769

Merged
merged 2 commits into from
Sep 24, 2024
Merged

Conversation

Gustry
Copy link
Member

@Gustry Gustry commented Sep 18, 2024

No tested, no idea.

Just to think about 3liz/lizmap-plugin#604 and 3liz/qgis-lizmap-server-plugin#87 about the migration from BootStrap 2 to BootStrap 5 in #4455

CC @mdouchin @nboisteault and @mind84

@github-actions github-actions bot added this to the 3.9.0 milestone Sep 18, 2024
@mind84
Copy link
Contributor

mind84 commented Sep 19, 2024

@Gustry,

this $projectInfos->version returns a string, something like "3.9.0-pre". I think the version could easily be extracted from this string and converted in number directly on php side. If it's reliable, form me is good then

Thanks

@Gustry
Copy link
Member Author

Gustry commented Sep 19, 2024

I will first wait for @nworr and @laurentj about any slowdown if it's done at each HTTP request ?

For the string versus number, the advantage of strings is that it's more precise (beta, rc etc) if we need it later on Python side.

We can still use the string to decide between BS2 or BS5.

@Gustry
Copy link
Member Author

Gustry commented Sep 20, 2024

After a discussion with @nworr :

  • it's too expensive to load this XML to know this version on each HTTP requests

Either, only do this on a GetFeatureInfo request, when we need it.

Or even easier, add a BOOTSTRAP_VERSION=5 in the HTTP request. It's a hardcoded string.

@nworr
Copy link
Contributor

nworr commented Sep 20, 2024

Maybe a more generic variable name ? CSS_FRAMEWORK=BOOSTRAP5

@Gustry Gustry changed the title Send the LWC version to QGIS Server Request GetFeatureInfo with Bootstrap5 Sep 23, 2024
@Gustry
Copy link
Member Author

Gustry commented Sep 23, 2024

PR updated and ready I guess.

It needs the branch 3liz/qgis-lizmap-server-plugin#87

@Gustry Gustry marked this pull request as ready for review September 23, 2024 10:38
@mind84
Copy link
Contributor

mind84 commented Sep 23, 2024

@Gustry,

It needs the branch 3liz/qgis-lizmap-server-plugin#87

I see you updated the PR, can I do something?

Thanks

@Gustry
Copy link
Member Author

Gustry commented Sep 23, 2024

No, I just pushed to your branch just now. Tests are now passing.

This PR #4769, and desktop side 3liz/lizmap-plugin#604 and server side 3liz/qgis-lizmap-server-plugin#87 are now ready ;-)

@mind84
Copy link
Contributor

mind84 commented Sep 23, 2024

@Gustry,

ok! Thanks for doing all the job! ;-)

@Gustry Gustry merged commit 0f04a94 into 3liz:master Sep 24, 2024
13 checks passed
@Gustry Gustry deleted the lwc-version branch September 24, 2024 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants