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

[Bug] Add embedded layers to keyValueConfig object #4847

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mind84
Copy link
Contributor

@mind84 mind84 commented Oct 7, 2024

Embedded layers are not taken into account when Lizmap requires the the key value configuration for attribute table display.

I did a little refactoring on handling embedded layers during projects loading (it's in a separated commit, but it is strictly related to this bug)

Funded by Faunalia

@github-actions github-actions bot added this to the 3.9.0 milestone Oct 7, 2024
@mind84
Copy link
Contributor Author

mind84 commented Oct 7, 2024

Backport in 3.8, if possible.

Thanks

@Gustry
Copy link
Member

Gustry commented Oct 7, 2024

Sorry, I just renamed the project, to not only cover "editing capabilities" in #4846. Can you rebase and update the project name ?

@Gustry Gustry added run end2end If the PR must run end2end tests or not backport release_3_8 sponsored development This development has been funded labels Oct 7, 2024
@mind84 mind84 force-pushed the attribute_table_embed_keyvalue_config branch from 94c24fd to 22a0571 Compare October 7, 2024 14:10
@mind84
Copy link
Contributor Author

mind84 commented Oct 7, 2024

Can you rebase and update the project name ?

I think is good now

*
* @return \SimpleXMLElement[]
*/
public function getXmlLayer($layerId, &$embeddedRelationsProjects = null)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this parameter was added in 3.8 or before ?

I read a few lines before L645 650 that this method is deprecated already. But I was wondering if we should mark this attribute as deprecated as well instead of removing ? I haven't checked if this function was called in another Lizmap module with 2 parameters ? (and it's an API break, all modules must be checked)

List of public modules : https://packagist.org/packages/lizmap/

just asking

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release_3_8 run end2end If the PR must run end2end tests or not sponsored development This development has been funded
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants