Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Changed profitability analysis report width #26150

Conversation

nemesis189
Copy link
Contributor

@nemesis189 nemesis189 commented Jun 22, 2021

Adjusted the width of Profitability Analysis Report to fit the screen and reduce white space

Before
image

After
image

@coveralls
Copy link

Coverage Status

Coverage remained the same at 42.699% when pulling a446d61 on nemesis189:changed-profitability-analysis-report-width into e3a697c on frappe:develop.

@@ -168,21 +168,24 @@ def get_columns(filters):
"label": _("Income"),
"fieldtype": "Currency",
"options": "currency",
"width": 120
"width": 305
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nemesis189 Can you add some screenshots of the report in description. Want to see how it looks now. Also why 305 and 307 and not some rounded whole no like 320 or 300?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adjusted the values for the table to fit the whole display, lesser values would leave a noticeable amount of space and looks quite asymmetric

@deepeshgarg007
Copy link
Member

@nemesis189 backport this to version-13-hotfix branch too

@deepeshgarg007 deepeshgarg007 merged commit e8817f9 into frappe:develop Jun 23, 2021
asoral pushed a commit to asoral/erpnext that referenced this pull request Nov 12, 2021
…-analysis-report-width

fix: Changed profitability analysis report width
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants