Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor!: remove public interface of util.path.traverse_parents #3525

Merged
merged 1 commit into from
Dec 23, 2024

Conversation

dundargoc
Copy link
Member

@dundargoc dundargoc commented Dec 22, 2024

Work on #2079.

@dundargoc dundargoc marked this pull request as ready for review December 22, 2024 21:05
@dundargoc dundargoc requested a review from glepnir as a code owner December 22, 2024 21:05
@dundargoc dundargoc force-pushed the refactor/traverse_parents branch from eed9a5b to c6586b5 Compare December 22, 2024 21:05
@dundargoc dundargoc changed the title refactor!: remove util.path.traverse_parents refactor!: remove public interface of util.path.traverse_parents Dec 22, 2024
@dundargoc
Copy link
Member Author

dundargoc commented Dec 23, 2024

Removed the public function since none of the configs actually use this and I don't think it's used much in the wild anyway, so figured this should be fine. If this is too breaking lemme know and I'll instead focus on adding functionality to core vim.fs instead.

@glepnir
Copy link
Member

glepnir commented Dec 23, 2024

If this function is not used internally, it can be safely removed. I think we never recommend any configuration to use the function encapsulated here. vim.fs is always our direction

@justinmk
Copy link
Member

adding functionality to core vim.fs

Related: neovim/neovim#25154

@dundargoc dundargoc merged commit c580f34 into neovim:master Dec 23, 2024
11 checks passed
@dundargoc dundargoc deleted the refactor/traverse_parents branch December 23, 2024 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants