Doing the #100DaysOfCode challenge for the second time. I did this last year and I saw a lot of improvement in the way I solve problems and I really like that so I'm doing it again. This is my public commitment post. I'll be dropping day 1's update when my day is over :)
proud of what I was able to accomplish. I've learned a lot, I've gotten about 90% of the mvp done for the daily bingo project, and I've picked up some nice habits. Now, I need to get in some sleep before my body gives out on me :sweat_smile:
#100DaysOfCode
100/100
"Fresh eyes tomorrow" decided to look at other things. I fixed a bug in my layout that was preventing user data from being reactive, fixed another bug in the cards list where it would not refresh the cards after one had been updated, finally figured out...
how to add a preserve scroll feature for the chat page so it a) scrolls to the bottom when the page loads and b) preserves scroll position when the nested details page is open.
**Thoughts**
I definitely planned to get more done before the end of this challenge, but I'm still...
#100DaysOfCode
99/100
I got Ably to connect properly, but I'm still not handling message sending correctly. I fixed a bug I noticed in the groups route, added a redirect rule to *try* to account for a Clerk issue that gives me a 'too many redirects' error.
#100DaysOfCode
98/100
I broke something, I'm just not sure what yet. I know it has something to do with how I'm connecting to Ably (my Pub-sub provider). I did manage to fix the server selection error after going through the MongoDB docs. Hopefully that was a more permanent fix.
#100DaysOfCode
97/100
- Fixed a bug that tried to use user data before it had been fetched, and another that was attempting to connect with the ably channels before the user was signed in.
- Currently stuck trying to figure out why I'm having a mongo server selection error again
I read once that caching the array length helped save time in long loops. It did not occur to me that the writer of that article was not referring to js where the array is in fact an object with a length property (and so already cached) ๐คฆ๐ฟ
It has just occurred to me
#100DaysOfCode
94/100
Added a session storage plugin to save the currently opened card; made a list card component for the cards route.
I'm going to put refactoring on the back burner for the remainder of the challenge so I can focus on finishing the MVP for this project.
#100DaysOfCode
93/100
- Fixed all auth references to use Clerk's composables; made a custom composable for fetching the authenticated user and saving user data to local storage; setup the composable to be called when the app loads and when the user signs in or up.
saved to the database).
3. Moved the daily card template + logic and the landing page into components so the index route can conditionally render them depending on whether the user is signed in.
4. Started changing my auth references to use Clerk's composables.
#100DaysOfCode
92/100
1. Moved the logic for confirming db connection to a middleware to keep my code dry.
2. Modified the webhook endpoint so it handles user creation as well as session creation (I did this to handle a case where the user exists on Clerk but hasn't been...
#100DaysOfCode
91/100
- Finished setting up the endpoint to save user to the db when created.
- Had a bug of my db not being connected. Figured out today it's because Netlify uses severless functions. Resolved this by moving the logic for connecting the db to the event handlers.
#100DaysOfCode
90/100
- Decided to port to Clerk for IAM. I'm making this decision because my current IAM solution feels too hack-y. Clerk has a more seamless feel to its implementation, and there was really no reason for me to reinvent the wheel here
#100DaysOfCode
88/100
- Worked on the mentorHub partner ui; completed the type ahead feature in the addContact form, built the admin route and the add person route.