[WIP] Add lints to enforce type safety #18
Closed
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.
Plan: Add Type-Safety Lints to fd_lints
Based on the existing lints that focus on type-safety (
avoid_as,avoid_non_null_assertion, and the unmodifiable view mutations), I will add the following complementary type-safety lints:avoid_dynamic_calls- Warn when calling methods/properties on dynamic typesprefer_is_empty- Prefer.isEmptyover.length == 0for better null-safetyavoid_returning_null- Avoid explicitly returning null (prefer nullable return types)doc/directorylib/main.dartto register the new lintsREADME.mdto include the new lints in the tableCHANGELOG.mdwith the new additionsdart analyzeon the example💡 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.