Working on Modals... So hard..

I'm building a modal in Nuxt.\ The idea is to open it as a modal when adding or editing, so you can view and edit the data. For the main login authentication modal, I used \$refs.\ But apparently, Vue doesn't recommend doing that... So... after a lot of trial and error... I made a Modal component...\ It took a day. . I pass the data in through a Slot, and when a button is clicked inside, it calls an event on the parent component again. For normal modal usage, I'll keep reusing this component... Wow\... seriously... I thought I was almost done...\ I can't get vee-validate working in the modal..\ Is it because I put it in through a Slot? What on earth could be the cause..\ My head hurts so much. Whew\..... I'm stressed out...\ This just isn't getting solved at all.. (2 hours later... 4:40 a.m.)\ It's possible to use components with vee-validate.. And I can display errors here... But this is the biggest problem.. Let's say I clicked the \[Add] button in the modal, but the request was rejected because the name already exists..\ Then, obviously, while the modal is still open, I need to update the error value.. But... it doesn't seem like that's working.....\ From the start, if I use Provider or Observer, it seems like I can't use the ErrorBag.... So is it even possible to reuse the modal component itself? It isn't, is it? Then do I have to make a separate modal component for each use case.. Sigh... my head's gonna explode.. I'm putting it in a Slot inside the component.. and the problem is when I put it in through a Slot here... Could Provider solve it? Ugh! This was probably a saved post from 4 days ago.. vee-validate had been updated to version 3.0.. So it took even longer because I had to change everything to match that version, but in the end, everything worked..\ I finished all the Role and Permission parts.. ``` $validator = Validator::make($request->all(), [ 'name' => 'required|string|unique:roles,name,'.$id.',id', 'permission' => 'required', ]); ``` Especially here... when updating, I needed to make an exception for duplicate nicknames, so I handled that with\ unique:roles,name,'.\$id.',id'.. ``` $role->update($request->except('permission')); ``` Here.. I thought that when updating, any columns that weren't in all() would be ignored... I guess not...\ But now that I think about it, using only seems better than using except..\ I'll change it.. ``` $role->update($request->only(['name'])); ``` Changed it... I'll use only, and it's probably better not to include unnecessary things like id or update_at.. ``` if($role->updated_at->toDateTimeString() === $request->updated_at) { ``` And... I get updated_at from the form, and show an error if it doesn't match..\ That way, I can prevent someone from making changes based on stale data when multiple people are editing at the same time... After a lot of trial and error... anyway, I finished all the permission-related parts.. Now I need to test whether the permissions can be assigned on the frontend and backend, and whether everything works when editing...

More posts