Change EncrytedFs::read_dir/plus to only show children

[someotherself]

The fs_api layer must allign with rust standard library.
std::fs::read_dir only iterates over children. Ours should do the same.
Changes are needed for:

1. encryptedFs function,
2. tests for encryptedFs and for Path
3. docs for Path method

[Hrushi20]

Hey! I was trying out both on my system. I see Directory Entry for Encrypted::fs and DirEntry for rust std::fs. What do you mean by align our api to iterate only over children? Can you explain with below example?

[someotherself]

Hey! I was trying out both on my system. I see Directory Entry for Encrypted::fs and DirEntry for rust fs. What do you mean by align our api to iterate only over children? Can you explain with below example?

When running std::fs::read_dir, (I'm testing it on linux and windows) it will only iterate over children and ignore . and ...
read_dir and read_dir_plus in our EncryptedFs current include . and ...
In your example, ino: 1 is root (or parent) dir - .. When running fs.read_dir(1), it should show only the RegularFile.
This is not exactly a bug however, our own fs_api::fs::read_dir will be using these functions and we want it to be 100% interchangeable with std library.
Are you getting a different behaviour out of std::fs::read_dir?

[radumarias]

@someotherself let's go like you get the output

[radumarias]

@someotherself how's with this task?

[someotherself]

@radumarias There's a few other PR's dependent on the existing code. I thought I'd leave this until after those PR's are merged.

[radumarias]

yes, please wait until I review them, sorry for the delay is if possible to send me all PRs related to this just to make sure I don't miss any? And in the end, it's not the years in your life that count. It's the life in your years.

…

On Fri, Apr 11, 2025, 10:17 someotherself ***@***.***> wrote: @radumarias <https://github.com/radumarias> There's a few other PR's dependent on this code. I thought I'd leave this until after those PR's are merged. — Reply to this email directly, view it on GitHub <#273 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5TC4EASSFUKRNACSNQDAT2Y6CCFAVCNFSM6AAAAABUDDN6GGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJWGMZDKNRUHA> . You are receiving this because you were mentioned.Message ID: ***@***.***> *someotherself* left a comment (xoriors/rencfs#273) <#273 (comment)> @radumarias <https://github.com/radumarias> There's a few other PR's dependent on this code. I thought I'd leave this until after those PR's are merged. — Reply to this email directly, view it on GitHub <#273 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5TC4EASSFUKRNACSNQDAT2Y6CCFAVCNFSM6AAAAABUDDN6GGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJWGMZDKNRUHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[someotherself]

True :D

I think it's just 2 - #283 and #264