[blockly] Provide HTTP request block

[stefan-hoehn]

This is finally the missing HTTP Request block for Blockly.

In this case I tried to make the block as concise as possible. Therefore it contains to block mutation switches that allow hide/unhide timeout and headers if they are needed or not.

[relativeci]

Job #1725: Bundle Size — 11.03MiB (+0.09%).

6b1452e(current) vs 9096d6d main#1724(baseline)

Warning

Bundle contains 19 duplicate packages – View duplicate packages

Bundle metrics   2 changes

	Current Job #1725	Baseline Job #1724
Initial JS	1.85MiB	1.85MiB
Initial CSS	607.92KiB	607.92KiB
Cache Invalidation	17.29%	18.17%
Chunks	220	220
Assets	242	242
Modules	3090(+0.03%)	3089
Duplicate Modules	164	164
Duplicate Code	1.77%	1.77%
Packages	150	150
Duplicate Packages	18	18

Bundle size by type   1 change 1 regression

	Current Job #1725	Baseline Job #1724
JS	9.22MiB (+0.11%)	9.21MiB
CSS	889.4KiB	889.4KiB
Fonts	526.1KiB	526.1KiB
Media	295.6KiB	295.6KiB
IMG	140.74KiB	140.74KiB
HTML	1.24KiB	1.24KiB
Other	871B	871B

---

View job #1725 report View stefan-hoehn:http_blocks branch activity View project dashboard

[jimtng]

Can GET also set headers?

Another thing that would be handy is a query builder, ie given a dictionary of key value, append key=Val&key=val to the url

[stefan-hoehn]

Yes, by clicking on the H button, you can unhide that input. The T button unhides the timout. This allows the block to be very small in case you don't need it.

The Query Builder is an interesting idea. I could just add another input for the queries which allows to add another map that supplies it and can be again unhidden by a (Q) button in the block. I like the idea.

[florian-h05]

In general LGTM, just a few comments, mostly wrt to code style.

[florian-h05]

LGTM, thanks!

[mherwege]

Another thing that would be handy is a query builder, ie given a dictionary of key value, append key=Val&key=val to the url

I am experimenting with this new functionality. I would be interested in this as well.

And another thing that could be useful in this context: a urlEncode function. Parameters in GET calls will have to be URL encoded. If extending the block with a query builder, the logic could include URL encoding the parameters.

[florian-h05]

The groundwork for this could be done inside openhab-js, where we could also check whether there already are npm modules to encode urls so we don’t have to write the logic ourselves ;-)

[mherwege]

so we don’t have to write the logic ourselves ;-)

Sure, I think so as well.

To give an idea, here is what I came up with purely in Blockly:

I think this can be made nicer. The URL encode function is of course not complete, but covers the need in my case.