Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • whats-open whats-open
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SRCT
  • whats-openwhats-open
  • Issues
  • #17

Closed
Open
Created Sep 29, 2016 by Nicholas J Anderson@nander13Owner

Simple API option

Currently, the API returns something like:

        "main_schedule": {
            "open_times": [
                {
                    "id": 556, 
                    "last_modified": "2016-08-29T00:35:40.011Z", 
                    "schedule": 101, 
                    "start_day": 0, 
                    "start_time": "11:00:00", 
                    "end_day": 0, 
                    "end_time": "18:00:00"
                }, 
                {
                    "id": 557, 
                    "last_modified": "2016-08-29T00:35:40.013Z", 
                    "schedule": 101, 
                    "start_day": 1, 
                    "start_time": "11:00:00", 
                    "end_day": 1, 
                    "end_time": "18:00:00"
                }, 
                {
                    "id": 558, 
                    "last_modified": "2016-08-29T00:35:40.020Z", 
                    "schedule": 101, 
                    "start_day": 2, 
                    "start_time": "11:00:00", 
                    "end_day": 2, 
                    "end_time": "18:00:00"
                }, 
                {
                    "id": 559, 
                    "last_modified": "2016-08-29T00:35:40.022Z", 
                    "schedule": 101, 
                    "start_day": 3, 
                    "start_time": "11:00:00", 
                    "end_day": 3, 
                    "end_time": "18:00:00"
                }, 
                {
                    "id": 560, 
                    "last_modified": "2016-08-29T00:35:40.028Z", 
                    "schedule": 101, 
                    "start_day": 4, 
                    "start_time": "11:00:00", 
                    "end_day": 4, 
                    "end_time": "18:00:00"
                }
            ], 
            "id": 101, 
            "last_modified": "2016-08-29T00:35:40.004Z", 
            "name": "Auntie Anne's", 
            "valid_start": "2014-08-24", 
            "valid_end": "2015-01-01"
        }, 
        "special_schedules": [], 
        "id": 100, 
        "last_modified": "2016-08-29T00:34:12.980Z", 
        "name": "Auntie Anne's", 
        "category": null, 
        "location": "Johnson Center"
    }

Which requires a lot of client side processing. It's a very verbose approach, but some applications might not need that. Ideally, we would have an endpoint available that returns just the current open_times and whether or not the facility is open.

Assignee
Assign to
Time tracking