8000
Skip to content

Hide empty lines in room detail view#3943

Open
johannaengland wants to merge 2 commits intoUninett:masterfrom
johannaengland:polish/hide-empty-lines-room-detail-view
Open

Hide empty lines in room detail view#3943
johannaengland wants to merge 2 commits intoUninett:masterfrom
johannaengland:polish/hide-empty-lines-room-detail-view

Conversation

@johannaengland
Copy link
Copy Markdown
Contributor

Scope and purpose

Fixes #3893.

I think we should hide the aliases if they are empty, since it is also done that way in the location detail view.

The room position can be discussed, but I think it simplifies the detail view.

Screenshots:
Before:
image

After:
image

Contributor Checklist

Every pull request should have this checklist filled out, no matter how small it is.
More information about contributing to NAV can be found in the
Hacker's guide to NAV.

  • Added a changelog fragment for towncrier
  • Added/amended tests for new/changed code
  • Added/changed documentation
  • Linted/formatted the code with ruff, easiest by using pre-commit
  • Wrote the commit message so that the first line continues the sentence "If applied, this commit will ...", starts with a capital letter, does not end with punctuation and is 50 characters or less long. See https://cbea.ms/git-commit/
  • Based this pull request on the correct upstream branch: For a patch/bugfix affecting the latest stable version, it should be based on that version's branch (<major>.<minor>.x). For a new feature or other additions, it should be based on master.
  • If applicable: Created new issues if this PR does not fix the issue completely/there is further work to be done
  • If it's not obvious from a linked issue, described how to interact with NAV in order for a reviewer to observe the effects of this change first-hand (commands, URLs, UI interactions)
  • If this results in changes in the UI: Added screenshots of the before and after
  • If this adds a new Python source code file: Added the boilerplate header to that file

@johannaengland johannaengland requested a review from a team March 27, 2026 08:50
@johannaengland johannaengland self-assigned this Mar 27, 2026
@johannaengland johannaengland added discussion Requires developer feedback/discussion before implementation frontend labels Mar 27, 2026
@sonarqubecloud
Copy link
Copy Markdown

@codecov
Copy link
Copy Markdown
codecov bot commented Mar 27, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.98%. Comparing base (9c8e7ea) to head (250eddb).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3943   +/-   ##
=======================================
  Coverage   63.98%   63.98%           
=======================================
  Files         627      627           
  Lines       46386    46386           
  Branches       43       43           
=======================================
  Hits        29680    29680           
  Misses      16696    16696           
  Partials       10       10           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown
Contributor
@Simrayz Simrayz left a comment

Choose a reason for hiding this comment

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

Nice, consistency go go 😄 I think putting aliases after description works well, as aliases are in a way just extra descriptors.

@johannaengland
Copy link
Copy Markdown
Contributor Author

Waiting for a review from Mr. NAV @lunkwill42 as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

discussion Requires developer feedback/discussion before implementation frontend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consider not showing empty fields in room detail view

2 participants

0