Edit Links component #20
Merged
l42luo
merged 0 commits from feat/linktree-editor-edit-links
into main
2 years ago
Loading…
Reference in new issue
There is no content yet.
Delete Branch 'feat/linktree-editor-edit-links'
Deleting a branch is permanent. It CANNOT be undone. Continue?
changed title from {-feat/linktree editor edit links-} to {+Edit Links component+}
You would need to rebase this locally first @l42luo
added 22 commits
main
Compare with previous version
marked this merge request as draft from 54d81e0660007b997cdb13f5c7aa376c0db83021
I don't think we need a styled div over here. Can we replace
<Container />
with a regular<div></div>
?Wait, it's a draft, so I won't review right now :)
changed this line in version 3 of the diff
added 1 commit
Compare with previous version
marked this merge request as ready
nit: remove these console logs
nit: let's not set the name for a new link, keep it empty instead
nit: delete these lines
nit: remove this function since we're not using it
replace with inline function from line 90 and use
e.target.checked
insteadreplace with inline function from line 90
nit: abstract this logic into a helper function and put this outside of the component body
I am using the name as the draggableId (it needs to be unique)
changed this line in version 4 of the diff
changed this line in version 4 of the diff
changed this line in version 4 of the diff
changed this line in version 4 of the diff
changed this line in version 4 of the diff
changed this line in version 4 of the diff
changed this line in version 4 of the diff
added 2 commits
Compare with previous version
added 6 commits
main
Compare with previous version
You should pull out these
svg
s into separate mini components so that we know what thissvg
is.Generally, it's not good practice to name types this way. For eg:
class FooClass {}
vsclass Foo {}
const barNumber = 1
vsconst bar = 1
In TypeScript, types that start with a
T
should be used when you're working with templates/generics.Also, why do we have a separate
types.ts
file?You can inline the type:
But this can look a bit weird 🤷
You can also export a
function
instead.Because
TEditLink
is being used in multiple files, I'll put it inutils/types
for now and we can change it afterwardshmmm I feel like both would add too much clutter, we should prob stick with declaring functions a certain way (in this case using arrow fns) and separating types instead of inlining it is better for readability imo
changed this line in version 6 of the diff
changed this line in version 6 of the diff
added 1 commit
Compare with previous version
added 3 commits
006f12c6
- 1 commit from branchmain
Compare with previous version
changed this line in version 8 of the diff
added 2 commits
Compare with previous version
added 1 commit
Compare with previous version
no any pls :P
actually we can fix this after we merge this PR
Do we need a div? How about react fragments instead?
<>...</>
added 1 commit
Compare with previous version
What do you think about renaming
LoginScreen
toEditorPage
and default export an unnamed function?changed this line in version 11 of the diff
changed this line in version 11 of the diff
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
approved this merge request
Reviewers