Version 2.0 Release #43
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Improved overall structure of logicCompile.ts - Centralized VSCode API calls - Removed unused declarations and abandoned dependencies
Refactor logicCompile.ts, Improve VSCode API Communication, and Clean Up Codebase
Refactor PieChart, update build configs, clean dist, and modularize code - Replaced VictoryPie with react-minimal-pie-chart for better performance - Updated tasks.json to include a build-ts-only task and clean dist folder before builds - Added Run Extension (TS Only) debugger configuration - Installed clean-webpack-plugin to clean dist folder before builds - Redesigned file structure for better modularity and maintainability - Modularized Node.js code for readability and reusability - Switched to pnpm for more granular dependency management - Reverted back to webpack from esbuild due to dependency issues, with plans to revisit esbuild - Removed Victory library to reduce build size by over 50%, refactored components accordingly PR #4
Ground-up Refactor/Rebuild
* recreaste compile error * tsconfig * diagnostics ready * launch config finalized * Add code to highlight full errored line --------- Co-authored-by: artmontinski <[email protected]> Co-authored-by: artmontinski <[email protected]>
This reverts commit bd1d0fe.
…bject 019aa87 transitional eslint object
* Add ESLint and Prettier configuration with GitHub Actions (pnpm) * Combine pnpm setup and lint/format checks into a single job * adjust Node version * style: auto-fix linting and formatting issues --------- Co-authored-by: artmontinski <[email protected]>
- Integrate saveLintResults command into eslintDiagnostics.ts - Add custom severity mapping to diagnostic messages - Implement conditional saving of lint results - Improve error handling in lintDocument function - Refactor and clean up unused code - Ensure consistency in message display methods - Optimize file system operations for better performance Co-authored-by: Benson Cheng <[email protected]> Co-authored-by: Kristian Schott <[email protected]>
…need to get progressionChart working correctly, need to get removeLibraryCommand working
Palette chart integration
- Refactor updateDashboard function to use 10 most recent results - Add current lint result to recent results before updating - Update data formatting for chart to use recent results
…ashboard updates - Implement hash-based comparison for reports to avoid duplicate entries - Add hash function to generate unique hashes for individual reports - Modify saveLintResultToLibrary to use hashed results for comparison - Update updateDashboard function to include the most recent lint result - Integrate dashboard updates with "on active file" toggle functionality This commit improves the efficiency of report library storage by avoiding unnecessary duplicates and ensures that the dashboard always displays the most up-to-date information, including the report on which it's triggered.
Enhance report I/O process and fix focus issues
- Update toggleLintActiveFile and toggleLintAllFiles functions - Improve status bar update logic to reflect current linting state - Implement 'resetLib' command to delete Summary_Library folder - Add confirmation dialog before resetting the library - Register 'ludwig.resetLib' command in extension initialization
- Create 'showLintingMenu' command for changing linting mode - Implement disableLinting function for turning off all linting
- Add icons and emojis to quick pick menu - Implement markdown formatting in menu item descriptions - Update showLintingMenu function to handle new dashboard/report option
- Adjust linting frequency to better handle VS Code's autosave feature - Enhance onDidChangeTextDocument listener with proper timeout handling - Ensure reports are only generated when linting is enabled - Optimize performance by reducing unnecessary lint operations
Enhanced Linting Functionality and User Interface Improvements
Enhance Linting Functionality and Optimize for Autosave
- Enhance compileLogic to use accurate position data - Optimize performance for processing large HTML documents - Refactor code for better maintainability and readability Authored-by: Spencer Hezzelwood <[email protected]>
HTML Integration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ludwig VS 2.0: Comprehensive Accessibility Toolkit for HTML and React
🌟 Overview
Ludwig VS 2.0 represents a major leap forward in our mission to make web accessibility easier and more efficient for developers. This release introduces powerful new features, expands our accessibility standards coverage, and significantly improves the user experience.
🚀 Major Features and Improvements
1. Advanced ESLint Integration
We've taken our ESLint integration to the next level, providing developers with more powerful and flexible linting capabilities:
2. Enhanced Linting and Reporting
We've revolutionized our approach to linting and reporting:
3. Intuitive User Interface Improvements
4. Performance Optimizations
5. Expanded Accessibility Standards Coverage
6. Improved Developer Experience
🛠️ Technical Improvements
📊 Visualization Enhancements
🧹 Code Cleanup and Maintenance
📚 Documentation
🚦 Breaking Changes
🗺️ Roadmap
🤝 Feedback and Contributions
Your feedback and contributions are crucial to making Ludwig ES the best accessibility toolkit it can be. We encourage you to:
Thank you to all the contributors who have helped make Ludwig ES 2.0 a reality. Together, we're making the web more accessible for everyone!
Download Ludwig VS 2.0 on MS VSCode Extension Store. Scheduled for release July 27 2024