Identify superfluous/missing blocks

[ThomasJejkal]

While playing around I came up with the following setup:

The idea was to modify elements of the given list and put them into another list, i.e., a variable that can be used afterwards. The issue is, that there are barely no blocks fitting in the "do" section. Some blocks I could imagine are a date formatting block, regex processing, or resolution using an external service.

As there are also other blocks where I'm not sure if they are useful, an investigation of potential usage scenarios and cleanup/extension of the block offer could be required.

[Pfeil]

I am investigating the issue, but I think it should be possible right now. Although it might be a bit cumbersome, and we should consider some convenience block or a preset for use cases which occur often. I will look into how this would need to look currently.

Note: The for each block will not generate code like this, it would need to be within a function block. The fact that we can put a loop in the record (or a profile in a loop) is a bug.

---

The current way could look like this, which is admittedly a lot of fiddling for such a small task:

→ We should make sure to have some high level blocks for common tasks, avoiding variable fiddling needs.

• The most obvious solution would be to adapt functional patterns as blocks. Like filter, map, and others.
• We currently can create empty lists, but we can't really extend / append to them.
• Dates are pretty essential. Maybe we should have a block for this.