Fix formatting and linting issues across codebase #1
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.
Resolved 200+ formatting inconsistencies and linting errors preventing clean builds and CI passes.
Changes
operator-linebreak,if-newline,quotes,indent,number-literal-case) to allow Prettier to handle formattingjiti,@vue/compiler-sfc) required by ESLint toolingNotable fixes
All remaining linting warnings are non-critical (JSDoc parameter names, intentional type redeclarations).
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
ofcncog2cu-dsn.algolia.net/usr/local/bin/node node /usr/local/bin/yarn add -D jiti ACCEPT(dns block)/usr/local/bin/node node /usr/local/bin/yarn add -D @vue/compiler-sfc(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.