fix: resolve aligment issues (#649)

[stealth-bombeer]

Brief Information

This pull request is in the type of (more info about types):

• build
• ci
• docs
• feat
• fix
• perf
• refactor
• test

Related issues (all available keywords):

• fix [improvement] CSS styles update needed to ensure aligned #649

Details

Currently the Developer Network/Most Participated Repo of user profile is not aligned leading to misalignments of the description and the graph I've added appropriate styles to the following components such that they align according to their parent component

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA

Others

N.A

[wxharry]

@stealth-bombeer Thank you for the contribution! Could you please add some screenshots to show the UI changes? It would be very helpful for others to check out. Thanks!

[stealth-bombeer]

@wxharry , i've added pictures when screen is resized as well in fullscreen mode same changes are being applied to Most Participated Repo

[wxharry]

@wxharry , i've added pictures when screen is resized as well in fullscreen mode same changes are being applied to Most Participated Repo

Thanks, nice work! Could you also align the graph title and the period? I believe they are supposed to be in the same row. 😆

[stealth-bombeer]

@wxharry , i've added pictures when screen is resized as well in fullscreen mode same changes are being applied to Most Participated Repo

Thanks, nice work! Could you also align the graph title and the period? I believe they are supposed to be in the same row. 😆

They are aligned in a block manner because when the screen becomes smaller the period tends to float on the graph container which lead to issue(#647 ) collapsing of graph and description ,even the Perceptor Tab of Repo is designed the same way 🙂

[wxharry]

They are aligned in a block manner because when the screen becomes smaller the period tends to float on the graph container which lead to issue(#647 ) collapsing of graph and description ,even the Perceptor Tab of Repo is designed the same way 🙂

The fix to the repo graphs is fine, the title and period is not separate. But this fix splits title and period into two lines which is not expected.

Also, the developer graphs also have the issue similar to #647. I wonder if you would like to fix that?

[stealth-bombeer]

They are aligned in a block manner because when the screen becomes smaller the period tends to float on the graph container which lead to issue(#647 ) collapsing of graph and description ,even the Perceptor Tab of Repo is designed the same way 🙂

The fix to the repo graphs is fine, the title and period is not separate. But this fix splits title and period into two lines which is not expected.

Also, the developer graphs also have the issue similar to #647. I wonder if you would like to fix that?

Alright got it,i'll try to make it responsive i.e i'll wrap the period to the next line only when it is colliding with the title

Untitled.1.mp4

does this make sense ?

[stealth-bombeer]

They are aligned in a block manner because when the screen becomes smaller the period tends to float on the graph container which lead to issue(#647 ) collapsing of graph and description ,even the Perceptor Tab of Repo is designed the same way 🙂

The fix to the repo graphs is fine, the title and period is not separate. But this fix splits title and period into two lines which is not expected.

Also, the developer graphs also have the issue similar to #647. I wonder if you would like to fix that?

I've committed all the changes as asked by you ,now you can take a look when you're free

[tyn1998]

Tested and LGTM, thank you so much @stealth-bombeer !

[tyn1998]

/approve

Hi @stealth-bombeer, we are currently developing v1.9.0, where we introduced a brand new feature loading mechanism. In this repo, most time we follow the GitHub flow, i.e. we only maintain a single master branch. However, considering that v1.9.0 is a huge task we cannot finish it in short time, we created another branch(v1.9.0) to work on with.

That is a trouble, we have to often pick changes in master and apply them to v1.9.0 again. The solution is to finish v1.9.0 ASAP 😆. So would you mind applying all changes you made to master so far to v1.9.0 and create a PR to that branch?

[stealth-bombeer]

/approve

Hi @stealth-bombeer, we are currently developing v1.9.0, where we introduced a brand new feature loading mechanism. In this repo, most time we follow the GitHub flow, i.e. we only maintain a single master branch. However, considering that v1.9.0 is a huge task we cannot finish it in short time, we created another branch(v1.9.0) to work on with.

That is a trouble, we have to often pick changes in master and apply them to v1.9.0 again. The solution is to finish v1.9.0 ASAP 😆. So would you mind applying all changes you made to master so far to v1.9.0 and create a PR to that branch?

Sure,i'll make all the necessary changes and create a PR for v1.9.0 branch 👍

[tyn1998]

git worktree is recommended for working on multiple branches(with different dependencies) in the same time :)