Rovers | Repository for the Rovers team | Robotics library

if I understand correctly, here is how you can do it :

Can you try the following amendment

The following Python code using the Qpid Proton library works with the Hono Sandbox.

The code in the data transform the date format '30/12/2019' to '2019-12-30' since only the later format is valid for the request.

The task appeared to be a bit harder as I thought in the beginning. This is how you can get the result you needed

There are many potential solutions here that I can think of. However, given the app needs to have predictable and reasonable user experience, herein I'm scoping out the issues first.

• Since a random resource is being requested each time, there's always a chance of it being null. Hence, multiple round-trips cannot be done away with (but can be reduced).
• Multiple HTTP round-trips, that too with the unpredictability of returning null several times, can be really frustrating user experience.

Below are the potential ways (in increasing order of complexity) this can be dealt with.

1. The simplest solution is to implement logic on the repository level, wherein the function getCuriosityPhotos is responsible to request the api resource indefinitely till it responds with a not null data. This will solve the core issue that the user will eventually be shown something (but it might take a hell lot of time).

(PS- You'll also need to delegate the random number generation as a potential service available to the repository.)

1. To reduce the number of requests and hence wait-time for the user, you can save to the in-app database, the request params as well as the response. Thus, your database can act as a single source of truth. Hence, before making a request, you can query the database to check if the app had previously requested the same params earlier. If it did not, dispatch the request else if it did, then there's no need to request again and you can use the previous result. If it was null, regenerate another random number and try again. If it was not null, serve the data from the database. (This is a good enough solution and as more and more requests & responses are saved, user wait time would continually reduce)

(Note: In case the endpoints do not respond with static data and the data keeps changing, prefer using an in-memory database than a persistent database such as SQLite)

1. The app can run a background service that continually (by iterating over all possible combinations of the request params) requests and saves the data into the database. When the user requests random data, the app should display a random set of data from within the database. If the database is empty/does not meet a threshold of having at least n number of rows in the database, the app can perhaps show an initialization setup UI.

Pro-tip: Ideally (and in case you are building a product/service), mobile apps are meant to be very very predictable and have to be mindful of a user's time. Hence, the very task of requesting data from such resources should be a task of a backend server and database which operate some sort of service to fetch and store data and in-turn the app would request this server to fetch data amongst this subset which does not have any null values.

I've answered this question from a perspective of solving the problem with varying granularity. In case you need help/advice on the technical implementation part, let me know, I'll be happy to help!

You can use LISTAGG(equipment_type,',') WITHIN GROUP (ORDER BY ) along with adding other (non-aggregated) columns to GROUP BY list :

First convert YYYY-MM-DD date string to Date

The problem is that in your Card component, you navigate using history api and you specifically set state in the push.