Header - Add authenticated user organization in hidden fields

[mdouchin]

This allows a JavaScript script to get the current user organization and use it in the editing form.

Ticket : #

Funded by Ville d'Avignon https://cartes.mairie-avignon.com

[mdouchin]

cc @sigavignon

[Gustry]

Tests added ;-)

Linked to #3963 and #3960

[mdouchin]

@Gustry thanks a lot for the tests. Do you think we should also add other fields (city, postcode, etc.) ?

[Gustry]

If more are added, I would prefer something cleaner (and revert your change in the first commit), using data attributes ?

I'm curious what other websites do ? Do they expose all "sensible" data into the frontend ? (with extensions, plugins ...)

[rldhont]

@mdouchin this data could be exposed through jsvars, like dataviz, action, filter, isn't it ?

[Gustry]

Way more comfortable to use

[github-actions]

Read only

Summary

Tests 📝	Passed ✅	Failed ❌	Skipped ⏭️	Pending ⏳	Other ❓	Flaky 🍂	Duration ⏱️
24	24	0	0	0	0	1	38.8s

Flaky Tests

Flaky Tests 🍂	Retries
🍂 Axis Orientation NEU for EPSG:3044	1

Github Test Reporter

🔄 This comment has been updated

[Gustry]

Is there still something to do ?

I think let's merge but other fields should go in a kind of API, like, like a global function currentUserLogin() ...

[mdouchin]

ok for merging, and agree with you regarding API

[3liz-bot]

The backport to release_3_8 failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply 00fa45a30... Header - Add authenticated user organization in hidden fields
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

stdout

Auto-merging lizmap/modules/lizmap/templates/user_menu.tpl
CONFLICT (content): Merge conflict in lizmap/modules/lizmap/templates/user_menu.tpl

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release_3_8 release_3_8
# Navigate to the new working tree
cd .worktrees/backport-release_3_8
# Create a new branch
git switch --create backport-5288-to-release_3_8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 00fa45a30d995e447b139c8306d1d9c7d5988352,9c444a592d70b978deab382e250c8d25197e2f33
# Push it to GitHub
git push --set-upstream origin backport-5288-to-release_3_8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release_3_8

Then, create a pull request where the base branch is release_3_8 and the compare/head branch is backport-5288-to-release_3_8.

[3liz-bot]

The backport to release_3_9 failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply 00fa45a30... Header - Add authenticated user organization in hidden fields
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

stdout

Auto-merging lizmap/modules/lizmap/templates/user_menu.tpl
CONFLICT (content): Merge conflict in lizmap/modules/lizmap/templates/user_menu.tpl

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release_3_9 release_3_9
# Navigate to the new working tree
cd .worktrees/backport-release_3_9
# Create a new branch
git switch --create backport-5288-to-release_3_9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 00fa45a30d995e447b139c8306d1d9c7d5988352,9c444a592d70b978deab382e250c8d25197e2f33
# Push it to GitHub
git push --set-upstream origin backport-5288-to-release_3_9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release_3_9

Then, create a pull request where the base branch is release_3_9 and the compare/head branch is backport-5288-to-release_3_9.