javleds / redspira-api Goto Github PK

When the user runs api-redspira, over 12:00 to 01:00 hrs, it always returns an extra record.

Place methods in alphabetical order if it is possible on interfaces and service providers.

By now, there are some code blocks which are duplicated, that is because we must analyze what is the behavior of the others endpoints, if they are similar to the current (device/area) then we must to simplify this code avoiding duplicted.

This is an example for AreaRegistryRepository and DeviceRegistryRepository:

    {
        switch ($intervalType) {
            case ApiParameters::HOUR_INTERVAL:
                return DateTime::createFromFormat(ApiParameters::ENDPOINT_DATETIME_FORMAT, $date);
            default:
                return DateTime::createFromFormat(ApiParameters::ENDPOINT_DATE_FORMAT, $date);
        }
    }```

There is no specific endpoint over redspira-api, but we could build it based on area/area-tree endpoint

This feature does not exists on base 'api-redspira' but we could build some based on specific time entries, for example, if the user requires las 3000 hours, we know that each day (except today) will have 12 records by day, then we cal simply calculate and paginate the records.

Verify if all API responses return the same data, in case that happens, then create a unique model for responses.

Change device interface method names to be equals than Area endpoint

Add a wrapper for get_monitores_ultima_lectura.php endpoint

Add a wrapper for get-area-tree.php