test: add tests for has_many.js

[dulerong]

test: has_many -> recomputePosition

chore: change web api

test: bindDestroyEvent

test: bindRemoveEvent

test: bindAddEvent

chore: refactored DOM manipulation, deleted useless code

test: bindRemoveEventCallBack

chore: apply new DOM node to tests

test: bindAddEventCallBack

refactor: event call back function

chore: change mock to spy

chore: change mock to spy

chore: lint

test: initSortable new assert

test: bindAddEventCallBack more assertions

chore: delete unnecessary code

refactor: move html elements to separate file

refactor: add html file for test

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behaviour?

Issue Number(s): N/A

Currently does not have test for has_many.js

What is the new behaviour?

• Added test for has_many.js

Other information

N/A

[dulerong]

@ilunglee
Hey, I decided to open a new branch, the previous branch, for some reason, when I tried rebasing, all the commits I merged from main branch, all scattered into individual commits (commits unrelated). Instead of being grouped in one single commit like "Merge from main branch"

Hence I cherry-picked my commit to a new branch and made a new PR.

I've answered your questions on the older PR, didn't want to force push into it, thought I might delete our conversations (I think it will delete the conversations?).

[ilunglee]

@ilunglee Hey, I decided to open a new branch, the previous branch, for some reason, when I tried rebasing, all the commits I merged from main branch, all scattered into individual commits (commits unrelated). Instead of being grouped in one single commit like "Merge from main branch"

Hence I cherry-picked my commit to a new branch and made a new PR.

I've answered your questions on the older PR, didn't want to force push into it, thought I might delete our conversations (I think it will delete the conversations?).

@dulerong,
I believe the reason why you have an extra commit (f4a9ce6) is because you used git pull --merge (this is the git pull default that runs git fetch and git merge) instead of git pull --rebase (git fetch and git rebase). See the following docs for more information:

• https://git-scm.com/docs/git-pull
• https://sdqweb.ipd.kit.edu/wiki/Git_pull_--rebase_vs._--merge

Force-pushing won't delete the comments. Please use the same PR (#98), and close this PR.

Thanks!

[dulerong]

@ilunglee Hey, I decided to open a new branch, the previous branch, for some reason, when I tried rebasing, all the commits I merged from main branch, all scattered into individual commits (commits unrelated). Instead of being grouped in one single commit like "Merge from main branch"
Hence I cherry-picked my commit to a new branch and made a new PR.
I've answered your questions on the older PR, didn't want to force push into it, thought I might delete our conversations (I think it will delete the conversations?).

@dulerong, I believe the reason why you have an extra commit (f4a9ce6) is because you used git pull --merge (this is the git pull default that runs git fetch and git merge) instead of git pull --rebase (git fetch and git rebase). See the following docs for more information:

• https://git-scm.com/docs/git-pull
• https://sdqweb.ipd.kit.edu/wiki/Git_pull_--rebase_vs._--merge

Force-pushing won't delete the comments. Please use the same PR (#98), and close this PR.

Thanks!

@ilunglee
Hey, I've forced push into PR #97, not sure why you mentioned #98 since that's not my original PR.

Will delete this branch later.

[ilunglee]

Thanks! Ooops, I meant #97 😆

[ilunglee]

closed in favour of #97