secureflow-cli: ux improvements in logs #290
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces several improvements and refinements to the SecureFlow CLI, focusing on usability, clarity of output, and robustness in plugin extraction. The most significant changes include enhanced handling of plugin directory structures during extraction, improved output formatting for token statistics, and minor adjustments to logging for a cleaner user experience.
Plugin extraction improvements
analyze-plugins.shto handle typical WordPress plugin directory structures, ensuring plugin contents are moved correctly and hidden files are preserved. Added cleanup of temporary extraction directories for robustness.CLI output enhancements
token-display.jsfor greater clarity, using more descriptive labels such asInput,Output,Context Usage, etc.animated-loader.jsto improve visual spacing in CLI output.Logging adjustments
ai-security-analyzer.jsto reduce console clutter during iterative security analysis. [1] [2]