ticktok-io / ticktok.io Goto Github PK

A little nice to have feature I thought that would be great is having the exact execution time next to the schedule in the ui

Describe the bug
When creating a clock uri & queue parameters are null. the new details parameters has them

To Reproduce
Steps to reproduce the behavior:

1. Create a clock POST /api/v1/clocks
2. see the response

Expected behavior
uri & queue should be filled with correct values for backward compatibility

0 validation on payload passed to api.

• can pass empty body
• can pass attributes not defined in the api

/queues?id=23434534,34546456,4564565,65767

Describe the bug
Every call to /clocks is restarting the cache so it doesn't actually cache anything

Expose the annotation via GET /clocks

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

• research develop slack bot/app
• pass to ticktok.io slack token
  • pass to Dockerfile env variable
  • create new component events
  • add token to yml file & consume on eventProperties
  • expose func/api fireEvent()
  • listen on tickPublish @rockem
• ticktok fire event to slack channel/bot/app

call to https://ticktok-io-dev.herokuapp.com/api/v1/clocks?access_token=your_token
body =>

{
  "consumerId": "test",
  "schedule": "every.5.seconds"
}

response is =>

{
    "schedule": "every.5.seconds",
    "consumerId": null,
    "id": "5ac92ac883ab490005c71f08",
    "url": "https://ticktok-io-dev.herokuapp.com/api/v1/clocks/5ac92ac883ab490005c71f08"
}

Something like
every.SUN|MON|TUE.at.15:30

Right now, when a clock was created but the client never connected to it. it remains PENDING and will stay that way forever

Describe the bug
Queue are auto deleted immediately when client loose connection

To Reproduce
Steps to reproduce the behaviour:

1. Create a clock
2. Disconnect client
3. queue is deleted immediately

Expected behaviour
Queues should wait for expiry time before delete

something like:
every.1.day.at.HH:mm
every.1.day@HH:mm

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.