Skip to content

Add aliases to location details page#3888

Merged
aleksfl merged 1 commit intomasterfrom
feat/show-location-aliases-in-location-details-page
Mar 20, 2026
Merged

Add aliases to location details page#3888
aleksfl merged 1 commit intomasterfrom
feat/show-location-aliases-in-location-details-page

Conversation

@aleksfl
Copy link
Copy Markdown
Contributor

@aleksfl aleksfl commented Mar 19, 2026

Scope and purpose

Fixes #3841.

before:
beforelocation

after:
with aliases
image

without
(same as before)

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
  • 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.

@aleksfl aleksfl requested a review from a team March 19, 2026 14:27
@aleksfl aleksfl linked an issue Mar 19, 2026 that may be closed by this pull request
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 19, 2026

Test results

    13 files      13 suites   25m 10s ⏱️
 2 899 tests  2 899 ✅ 0 💤 0 ❌
16 950 runs  16 950 ✅ 0 💤 0 ❌

Results for commit 92c6b57.

♻️ This comment has been updated with latest results.

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.83%. Comparing base (446fde8) to head (de1044f).
⚠️ Report is 18 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3888      +/-   ##
==========================================
+ Coverage   63.74%   63.83%   +0.08%     
==========================================
  Files         624      624              
  Lines       46154    46175      +21     
  Branches       43       43              
==========================================
+ Hits        29421    29474      +53     
+ Misses      16723    16691      -32     
  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.

@Simrayz Simrayz assigned aleksfl and unassigned aleksfl Mar 19, 2026
@aleksfl aleksfl requested a review from johannaengland March 20, 2026 09:21
@aleksfl aleksfl force-pushed the feat/show-location-aliases-in-location-details-page branch from c614bfe to efbbc5a Compare March 20, 2026 09:22
Copy link
Copy Markdown
Contributor

@johannaengland johannaengland left a comment

Choose a reason for hiding this comment

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

I noticed that for other attributes (like parent) that a line is only added if the attribute is not null, so to follow that pattern I would only show this line if a location has aliases

@aleksfl aleksfl requested a review from johannaengland March 20, 2026 09:31
@johannaengland
Copy link
Copy Markdown
Contributor

I noticed that for other attributes (like parent) that a line is only added if the attribute is not null, so to follow that pattern I would only show this line if a location has aliases

Funnily enough in rooms that is not the case - in that case you should create a follow up issue with a discussion tag where we should talk about if that difference in behavior is wanted and if not, which approach to follow - always show all lines or only should the lines where the content is not empty

@aleksfl
Copy link
Copy Markdown
Contributor Author

aleksfl commented Mar 20, 2026

I noticed that for other attributes (like parent) that a line is only added if the attribute is not null, so to follow that pattern I would only show this line if a location has aliases

Funnily enough in rooms that is not the case - in that case you should create a follow up issue with a discussion tag where we should talk about if that difference in behavior is wanted and if not, which approach to follow - always show all lines or only should the lines where the content is not empty

done here #3893

@aleksfl aleksfl force-pushed the feat/show-location-aliases-in-location-details-page branch from 92c6b57 to de1044f Compare March 20, 2026 09:41
@sonarqubecloud
Copy link
Copy Markdown

@aleksfl aleksfl merged commit b043992 into master Mar 20, 2026
16 checks passed
@aleksfl aleksfl deleted the feat/show-location-aliases-in-location-details-page branch March 20, 2026 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Show location aliases in location details page

2 participants