-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
feat: diff-view #1246
base: main
Are you sure you want to change the base?
feat: diff-view #1246
Conversation
Tag it as "WIP. @thecodacus @leex279 |
Detailed Overview of Recent Changes: 00bed77 - refactor: update FileModifiedDropdown styling and toast notification Enhanced Notifications: The toast notification used to confirm actions (like copying the file list) has been updated. This change makes the notification more prominent, ensuring users receive clear and consistent feedback when they perform file-related actions. 7e7fcec - fix: change markdown language detection to plaintext in DiffView Consistent Rendering: Handling markdown as plaintext prevents any misinterpretation of markdown syntax during the diff process, leading to a more consistent and readable output. 50d7c43 - feat: refactor file history tracking and add NoChangesView component NoChangesView Component: A new component—NoChangesView—has been introduced. This component clearly indicates to the user when no changes are detected between file versions, helping reduce confusion and providing a cleaner UI when files remain unmodified. f0dff04 - feat: improve diff view with robust file change detection and error handling Error Resilience: Additional error handling has been incorporated into the diff processing logic. In cases where diff computation might fail or encounter unexpected inputs, the system now responds more gracefully, providing useful feedback rather than a generic failure. 5fac72f - feat: add fullscreen and syntax highlighting to diff views Syntax Highlighting: Enhanced syntax highlighting within diff views makes code differences more visually distinct. This makes it easier to read and analyze changes, especially in large code blocks, by using color-coding that correlates with the underlying language syntax. de1891f - feat: add side-by-side diff view and enhance diff component flexibility Component Flexibility: The diff component has been made more flexible, supporting dynamic toggling between different diff views. This flexibility ensures that users have a choice in how they view the differences based on their current needs. 854bd2f - fix: revert package.json Stability: By reverting these changes, the package configuration is restored to a known stable state, helping maintain the integrity of the project’s build process. af444e6 - chore: remove unused imports in DiffView and Workbench components Optimized Bundle: Removing dead code also contributes to a slightly leaner bundle size, which may positively impact performance during compilation and runtime. 64a5f95 - feat: improve file changes tracking and diff view with enhanced history management Unified Experience: The strengthened tracking mechanism not only benefits the diff view but also supports other UI elements that rely on correct file history data, leading to a more coherent user experience. 40e09cb - fix: remove unused import in CodeComparison component Better Readability: This change also aids maintainability, making the component easier to understand and navigate for future improvements or debugging. I need someone to review the code and see if everything is correct @thecodacus @dustinwloring1988 @leex279. I still don't know why the changes appear several times in the same file even though it was modified once. I don't know if it's my fault or if Bolt opens the same file several times. The changes are being detected correctly regardless of how many times Bolt opens the file. There are still some improvements missing, but I don't know how to make them yet. The idea comes from a lack of seeing what Bolt was modifying. Meu.Video-1.mp4 |
@felvieira poderia me ajudar? |
Do que vc precisaa? |
Eu fiz o recurso so que arrumei todos os erros na base do codigo mais ainda aparece erros no console e não consigo resolver ainda estou aprendendo tudo então é meio dificil. Se tu tiver alguma ideia de como resolver. @felvieira |
Feature ready. It's not perfect but it's a start. |
This has nothing to do with PR. @Ridoy302583 |
I made this resource due to its lack because I wanted to know which lines and sections LLM was changing. It is not perfect yet. If someone is willing to help me optimize and eliminate redundancies, we can make a great resource to be added to the project. @thecodacus @wonderwhy-er @coleam00 @mrsimpson @Stijnus @dustinwloring1988