Get-Item ./.hidden-file fails with "Could not find item"

This behavior is on macOS 11.3.

Steps to reproduce

> Get-Item ~/.profile

Expected behavior

    Directory: /Users/nimazzuc

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-----           4/28/2021 12:25 PM            107 .profile

Actual behavior

Get-Item: Could not find item /Users/nimazzuc/.profile.

Environment data

WSManStackVersion = 3.0
PSEdition = Core
Platform = Unix
PSCompatibleVersions = 1.0 2.0 3.0 4.0 5.0 5.1.10032.0 6.0.0 6.1.0 6.2.0 7.0.0 7.1.3
GitCommitId = 7.1.3
OS = Darwin 20.4.0 Darwin Kernel Version 20.4.0: Fri Mar  5 01:14:02 PST 2021; root:xnu-7195.101.1~3/RELEASE_ARM64_T8101
PSRemotingProtocolVersion = 2.3
SerializationVersion = 1.1.0.1
PSVersion = 7.1.3

Additionally, the Mode thing is weird, shouldn’t that show the unix file mode?

[strega-nil]

This is… very weird to me, but fair enough. I still think it’s a bug (or at least a thing that should be changed), since hidden files aren’t “different” from regular files on unices.

[strega-nil]

Yeah, the fact that Get-Item requires -Force to “find” a hidden file just means that one should always pass -Force to Get-Item, since:

function Get-JsonElement {
  [CmdletBinding()]
  Param([Parameter(Mandatory)][String]$Path, [Parameter(Mandatory)][String]$JPointer)

  $File = Get-Item $Path
  ...
}

this is entirely reasonable code to write; additionally:

> Get-JsonElement .config.json '.foo.bar'

is also entirely reasonable code to write. There is no reason that putting these two bits of code together should fail, assuming .config.json exists, yet the default is that it does fail with a File Not Found error (which is… a very odd error, I must say).

EDIT: I would also argue that the behavior makes no sense on Windows either; why does Get-Item ~/AppData fail. That is very, very weird behavior.