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

[Feature] UX for ignored directories #202

Open
djzager opened this issue Jan 16, 2025 · 0 comments
Open

[Feature] UX for ignored directories #202

djzager opened this issue Jan 16, 2025 · 0 comments

Comments

@djzager
Copy link
Member

djzager commented Jan 16, 2025

konveyor/kai#452 gives us the ability to tell kai (and the analyzer) to ignore specific directories during analysis. We should provide users with more flexibility to define which directories are ignored during analysis. This feature would empower users to customize their excluded paths while maintaining compatibility with the analyzer's requirements.

Default Behavior: Automatically exclude the .vscode directory, allowing users to add or remove exclusions as needed.

Considerations:

  • Could we use .gitignore with something like https://www.npmjs.com/package/globby to just ignore everything git would ignore.
  • Do we need to use a .konveyorignore?
  • Maybe we could just expose this using .contributes.configuration in our vscode package.json

Other thoughts:

  • .gitignore syntax is complex and not entirely compatible with the analyzer, especially for patterns like ! and **.
  • For now, sending /path/to/workspace/.vscode directly to the analyzer is a practical stopgap measure to address immediate issues and enable the upcoming release.

This feature would enhance user control while ensuring the analyzer operates effectively with ignored paths.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant