-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/Actions/Configuration #4
Labels
enhancement
New feature or request
Comments
Merged
3 tasks
neilkakkar
pushed a commit
that referenced
this issue
Jun 10, 2024
* Add basic server (#3) * Add dependencies Tokio for async Axum for HTTP things Tracing for... tracing Serde for serialization * Setup simple hello world server * fmt * Server coming up, validating tokens * Spent ages trying to figure out the schema, which is currenly very fluid
neilkakkar
pushed a commit
that referenced
this issue
Jun 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our Clients need to be able to define Actions. We capture so many Events that if we just showed them all, the majority won't be useful.
Requirements
UX
We are going to use the same components for the right hand sidebar (the one used to map the Events to a Step). Since that also allows stringing together Steps into an Event.
The difference between the sidebar and the application, is that it's not possible to tag an Event as a Step in the application (it's necessary to go to our Client's app to do this with the sidebar).
In the application, it's necessary for a Client to be able to create an Action from existing Steps. The Client also needs to be able to create a new Step - which will link them to their own app's homepage, but with our sidebar opened.
(This also means, when a new Client is created, we need them to give their app's URL)
The text was updated successfully, but these errors were encountered: