Repository navigation
Conversation
…aints, visibility, etc.) take into account relationship changes
Collaborator
🍎 MacOS DMG universal buildsDownload a MacOS DMG universal build of this PR for testing. 🪟 Windows buildsDownload a Windows build of this PR for testing and for arm64. (Built from commit 24dca73) 📱 Android buildsDownload an Android arm64 build of this PR for testing. Other Android architectures🐧 Linux AppImage buildsDownload a Linux AppImage build of this PR for testing. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR implements support for dynamic virtual values within feature forms. A virtual field driving for e.g. a complex set of calculation based on multiple data provided fields will now always be up-to-date while editing a feature. This mimics the behavior in QGIS, which harmonizes one more UX between us and our big brother.
This comes in handy alongside a separate fix in this PR that insures relationship actions such as child feature addition / editing / and deletion trigger default value (and virtual field value!) updates when the relation_aggregate() function is used within the expressions that drive those values.