Closed vivekbopaliya closed 6 months ago
This looks pretty good for the most part, but we have some other proposed changes to the
CollectionList
component which will definitely conflict so I don't know what the plan is. #2376
Ahhhhh, it appears that several components were optimized along with two new Table and TableRow have been added. i didn't check the PR. my bad. although as it is pretty huge PR and i see it is in still development (as some of test cases got failed ;) ) hence, we are not sure when will it get merged as yet. in meantime, i am moving forward and fix the changes that you requested.
Additionally, we might want to seperate SketchListRow
from SketchList
and place it in its own file. I have worked on it and almost did wrap up migrating them into functional components and importing individual actions rather than prop drilling but eventually, it boiled down to failing one of 20 test errors even tho both components are completely working. I think while refactoring them, we will have to rewrite SketchList.unit.test
component as well.
Although I have never worked on testing before 😬, let me know if you want me to raise a PR, and we can further discuss what changes are required in the unit test component. (could be a mini collab?!)
This looks pretty good for the most part, but we have some other proposed changes to the
CollectionList
component which will definitely conflict so I don't know what the plan is. #2376Ahhhhh, it appears that several components were optimized along with two new Table and TableRow have been added. i didn't check the PR. my bad. although as it is pretty huge PR and i see it is in still development (as some of test cases got failed ;) ) hence, we are not sure when will it get merged as yet. in meantime, i am moving forward and fix the changes that you requested.
Yeah everything regarding the list/table components has been kind of up in the air due to this major rewrite which has been in the works for a long time.
Thanks so much for submitting this and I'm sorry it took a while to get to this!
Although it's a bigger PR, it does address a lot of the refactoring needs so I think we ultimately might want to go with https://github.com/processing/p5.js-web-editor/pull/2376, since it was raised first! In that vein, I'm going to close this one for now, but maybe some changes here could also be referenced in the other one as well?
Related to #2179 and #824
Changes:
I have verified that this pull request:
npm run lint
)npm run test
)develop
branch.Fixes #123