File.new "foo.txt" . parent returns Nothing

[radeusgd]

As shortly discussed a relative path will return Nothing if we cannot go 'up' anymore:

> File.new '.' . parent
>>> Nothing
> File.new 'foo.txt' . parent
>>> Nothing

To get the actual parent directory, we need to first get the absolute path:

> File.new '.' . absolute . normalize . parent
>>> (File X:\NBO)
> File.new 'foo.txt' . absolute . normalize . parent
>>> (File X:\NBO\enso)

I'm not exactly sure if this is right. I think ideally we should automatically switch to an absolute path if the relative parent cannot 'go up' anymore (although, keeping the path relative as long as possible). I.e. I'd suggest:

File.new "foo/bar/baz.txt" . parent # is relative `foo/bar`
File.new "foo.txt" . parent # becomes absolute `X:\NBO\enso`

However, maybe other approach should be taken.

Let's discuss if this is right or if another solution would be better, or maybe if we should just keep the current behaviour unchanged.

[enso-bot]

Radosław Waśko reports a new STANDUP for the provided date (2024-04-05):

Progress: Added some other edge cases to File.parent handling as well as changed how File.name works with .. and . It should be finished by 2024-04-09.

Next Day: Next day I will be working on the #9363 task. Fix a broken test issue on Enso_File path refactor. Add retries to HTTP tests (asked for by Hubert). Start work on path resolver integration.