search

cch5ng / job-tracker5-epic-stack

0 stars 0 forks source link

job mutations (create, update, delete) #5

Open cch5ng opened 7 months ago

cch5ng commented 7 months ago

start existing existing patterns then migrate over the loader logic to use graphql (need to fix the schema file for graphql)

cch5ng commented 6 months ago

bug with update submission, the pattern works for note update but not for job update; possibly need to run npm run prisma:db_pull and npm run prisma:generate; also don't forget to document in readme if there were any manual fixes that I had to apply before/after (prisma schema) the generate related to table relationships (like 1:many)

for notes, the requests looks like

GET /users/kody/notes/d27a197e 200 - - 63.290 ms
GET /users/kody/notes/d27a197e/edit?_data=routes/users+/$username_+/notes.$noteId_.edit 200 - - 17.541 ms
POST /users/kody/notes/d27a197e/edit?_data=routes/users+/$username_+/notes.$noteId_.edit 204 - - 25.810 ms

for jobs, the requests look like (2nd GET, the id is inconsistent and also hitting Submit never triggers the POST so maybe there is an issue going on with the form validation step)

GET /users/kody/jobs/b1993988-dc9b-47f8-a012-250472e8e74c/edit?_data=routes/users+/$username_+/jobs.$jobId_.edit 200 - - 21.014 ms
GET /users/kody/jobs/152a8ffb-250b-4289-a84c-3b214ea2e664?_data=routes/users+/$username_+/jobs.$jobId 200 - - 6.143 ms

at the job form/view, this is the last request made (but the Submit btn is not triggering the POST); Submit btn status is not changing; seems like the action is not getting triggered/run

GET /users/kody/jobs/b1993988-dc9b-47f8-a012-250472e8e74c/edit?_data=routes/users+/$username_+/jobs.$jobId_.edit 200 - - 33.355 ms
cch5ng commented 6 months ago

? upgrade the conform library (libraries) to v1? https://conform.guide/upgrading-v1

perhaps try to update the job table schema from db side to look more like note table; unclear why things like the form action in job is not getting executed but main difference seems to be something like Owner vs User (refering to ownerId) relation; it might affect the jobs and /jobId views logic though

(when printing out the navigation, the state is never getting to submitting so I imagine something is getting blocked at the validation level)