David Teather
David Teather
Incase people want to use a different form service provider but our pipelines POST applicantatlas.com/eventid/form with auth credentials Could add submissions for you. Need to explore this idea further since...
Ex: If user says they're under 18, expose a form they have to sign/upload Or if user marks "other" they can have a text field to specify below This seems...
requirements - [ ] should be able to specify in the form configuration a list of file types that should be allowed to upload - [ ] save it in...
I haven't looked at timestamp selector in awhile and I remember it was a nightmare so tbis probably should be a much larger change and refactor of the entire component
I initially made the event dashboard a SPA to share more information without getting annoying page refreshes on each click, however each sub tab or selected element should probably at...
We probably want to actually start branding especially if I make a video for initial release. - logo - favicon - LinkedIn - YouTube channel (probably cross post video on...
This will be tricky for - no duplicate submissions Maybe store an identifier in local storage, but this can be bypassed although might help people know if they submitted it...
On transactional logic like form submissions we don't want to save response if pipeline fails to run sorta stuff in `responses.go` comment on this
Not sure how actual companies test this, so it's something to investigate further but doing testing with like playwright or another browser software would be nice and check expected database...
example 1. select pipeline 2. set an event 3. save 4. go to settings tab 5. enable 6. save it's inconsistent on what the entity is since the changes fall...