This article first appeared in Hashnode
Intro
This is how I built a simple sprint dashboard using VueJS and used Amplify for backend, f...
For further actions, you may consider blocking this person and/or reporting abuse
Wooow .... this is soooo awesome!!! I sooo appreciate this @pubudusj absolutely great job.
This is an issue sometimes with some dev myself included .... the knowledge is there but we don't sit down and create something.
You have done that and kudos for an amazing work.
I really need to giddy up and create too. There is nothing cooler than creating stuff.
Thanks for your kind words @softwaresennin
Totally agree that nothing cooler than creating stuff (and share it with the community)
Who is saying putting everything in one table is best practice? There are several reasons amplify creates a separate table for every @model object type:
Many of the resources from github.com/alexdebrie/awesome-dyna... recommend single table design. Rick Houlihan in particular has some pretty convincing talks on why and how to achieve this.
Thank you, I will look into it.
Great. Thanks for the suggestions @enix79 . Really helpful 🙏
For better security you should use the @auth directive in the schema to only allow admins to create and update sprints.
Oh yeah. Thanks for the suggestion @hbj
AWS CodeCommit has no issue tracking. Turn this into a SaaS specifically for CodeCommit integration and you are now both popular and wealthy.
Thanks @andrewbrown . Yeah good idea :)
It's looking great. Would you like to try creating Kanban board as your next project
Yeah, maybe. I hope with some minor modifications this can be used as a kanban board as well.
This looks so good. Nice work.
Thanks @gudata
Not bad. Jumping on to new experiences are key to success.
Exactly. Also the guidance/suggestions from community is invaluable. Specially here in Dev.
Very insightful.
Thanks Yogun!