Change to temporarily avoid flow issues. Will be changed in next diffs

It is hardcoded in style.css (64px height + 1px for border):

div.main-header {
  height: 64px;
  background: var(--bg);
  display: flex;
  align-items: center;
  border-bottom: 1px solid var(--border-color);
}

Other styles calculating layout also have it hardcoded:

div.layout {
  height: 100vh;
  display: grid;
  grid-template-columns: 244px repeat(12, 1fr);
  grid-template-rows: 65px calc(100vh - 65px);
  grid-template-areas:
    'nav nav nav nav nav nav nav nav nav nav nav nav nav'
    'sBar app app app app app app app app app app app app';
}

So I'm not sure if there is an easy way to compute this value now, as it's already harcoded in multiple places

BTW, is there a downside in using the previous approach of returning the last available position when none are appropriate?

I can leave an old solution here - using the last available position

How should we handle the case if an empty array of availablePositions is provided? In such case, an old solution would return undefined although its result is not optional, as the flow doesn't check an existence of array element, isn't it?

Discussed this with Tomek. We will add a defaultPosition parameter to this function.