Change
Refactor range retrieval in form again
Issue description
Currently the form computes all URLs in JavaScript and then retrieves the resources. In 99% it is some list of topics, either a range or a instances of a topic type. This has some drawbacks. To mention two: the URLs are only known at runtime in the browser. It is therefore not possible to instruct a service worker to preload the form for a topic type. The assembly of the range request is quite difficult and thus would need some through tests.
Developer comments
The separation into subresources (range and search) is good, since these lists change more often than the schema.
The server controls now which range request will be issued by the form and when. This is the foundation to make it possible to compute the URLs that the form needs, which is necessary for PWA.
|
Work sessions7
Start |
2021-10-19T15:00:00
|
End |
2021-10-19T17:41:36
|
Participant |
Robert Cerny
|
Start |
2021-10-20T06:00:00
|
End |
2021-10-20T09:05:43
|
Participant |
Robert Cerny
|
Start |
2021-10-20T13:00:00
|
End |
2021-10-20T13:37:40
|
Participant |
Robert Cerny
|
Start |
2021-10-20T14:00:00
|
End |
2021-10-20T15:55:36
|
Participant |
Robert Cerny
|
Start |
2021-10-20T17:31:06
|
End |
2021-10-20T18:14:46
|
Participant |
Robert Cerny
|
Start |
2021-10-20T21:25:02
|
End |
2021-10-20T22:37:23
|
Participant |
Robert Cerny
|
Start |
2021-10-21T05:30:00
|
End |
2021-10-21T06:22:03
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.