Fix: draft behaviour and hydration error

[AdityaSingh-02]

What kind of change does this PR introduce?

Issue Number:

• Closes 🐛 Bug: Improve behaviour of Draft 2020-12 for mobile devices #483 🐛 Bug: Hydration Error #487
• Related to #___
• Others?

Screenshots/videos:

Before

Screen.Recording.2024-03-10.at.9.41.58.AM.mov

After

Screen.Recording.2024-03-10.at.9.54.39.AM.mov

If relevant, did you update the documentation?

Summary
1- Here I have fixed the behavior of the table before it was taking full width and there was not any overflow or width property.
2- I have also made changes in the release-notes.md, which was causing a hydration error and I made a change at line number 466. it was taking more than required width.

Does this PR introduce a breaking change?

• No

[DhairyaMajmudar]

Can you pls. remove the changes from yarn.lock and package.lock.json file since it is increasing the pr size.

[DhairyaMajmudar]

Also it will be good for users, if instead of applying overflow-auto , the 1x2 grid is converted into 2x1 grid as suggested in the issue : )

[JeelRajodiya]

I think you deleted the entire yarn.lock file.
As @DhairyaMajmudar mentioned, please leave the yarn.lock file as it is ( do not make any changes nor delete it )

[AdityaSingh-02]

I think you deleted the entire yarn.lock file. As @DhairyaMajmudar mentioned, please leave the yarn.lock file as it is ( do not make any changes nor delete it )

Yup, I deleted it completely(by mistake), I should have stashed changes before pushing, I will take care of it from next time, Till then what should I do? will it affect the code? since I have not added any new dependencies, the file has minor changes it should not affect code base(I might be wrong here)

[aialok]

@AdityaSingh-02, a better approach would be to clone the project from the beginning using Yarn and leave this as it is. Check out the README.md for more details.
Then, create a new branch with the same name as the one you used in this PR and make the required changes or you can copy-paste your work and force-push the changes to this PR branch. This will solve all your problems. Before cloning the project again, make sure you have fetched the latest upstream in your fork repository to avoid any conflict.

[AdityaSingh-02]

Heyy @JeelRajodiya I have reverted the changes, could you look at it again?

[JeelRajodiya]

@AdityaSingh-02, are you using npm ?

[AdityaSingh-02]

@AdityaSingh-02, are you using npm ?

yup

[JeelRajodiya]

@AdityaSingh-02, are you using npm ?

yup

yes, that is why the yarn.lock file is being modified.

You'll have use yarn instead of npm as suggested by @aialok in this comment

[AdityaSingh-02]

@AdityaSingh-02, are you using npm ?

yup

yes, that is why the yarn.lock file is being modified.

You'll have use yarn instead of npm as suggested by @aialok in this comment

okay got it, so should I do everything again or this works?

[JeelRajodiya]

@AdityaSingh-02, are you using npm ?

yup

yes, that is why the yarn.lock file is being modified.
You'll have use yarn instead of npm as suggested by @aialok in this comment

okay got it, so should I do everything again or this works?

can you run yarn install command and let me know if the yarn.lock file changes or not?
if the file changes commit and push those changes, that way the yarn.lock file will be back to it's original state.

[AdityaSingh-02]

Heyy @aialok @JeelRajodiya Thank you for your guidance, I followed your steps and pushed changes using yarn, and this time yarn.lock file didn't change

[JeelRajodiya]

Hey @AdityaSingh-02, You have resolved the problem.
but I want to bring this section of the issue #483 to your attention.

Let's just wait for the maintainer's review, before you proceeded any further

[benjagm]

It is not the solution I proposed but I like it. Thanks!