From 364bed1f9b5a73adc7af1b50c396f737469b626f Mon Sep 17 00:00:00 2001 From: Matthias Kuhn Date: Thu, 20 Dec 2018 10:28:50 +0100 Subject: [PATCH] =?UTF-8?q?Updated=2022nd=20Developer=20Meeting=20in=20A?= =?UTF-8?q?=20Coru=C3=B1a,=20Spain=20(markdown)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 22nd-Developer-Meeting-in-A-Coruña,-Spain.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/22nd-Developer-Meeting-in-A-Coruña,-Spain.md b/22nd-Developer-Meeting-in-A-Coruña,-Spain.md index 9f41c07..b3f2e13 100644 --- a/22nd-Developer-Meeting-in-A-Coruña,-Spain.md +++ b/22nd-Developer-Meeting-in-A-Coruña,-Spain.md @@ -113,6 +113,8 @@ If you are coming to a QGIS Developer event for the first time, you may be a lit The QGIS Expression builder offers [autocompletion support since QGIS 3.4](http://changelog.qgis.org/en/qgis/version/3.4-LTR/#code-completion-for-expression-builder). This vastly increases productivity while working with the expression editor. However, a lot of functions still don't show up their parameters `get_feature(...)` instead of `get_feature(layer, attribute, value)`. +This is also a unique possibility to get insights into the internals of the QGIS expression engine. + In this stream, we will learn how we can migrate functions so they show up with their parameters. If at the same time function descriptions and documentation can be improved, even better. **Stream leader:** Matthias Kuhn