Repository navigation
v0.6.0: per-endpoint field check, fewer false positives
Added
- Per-endpoint
FIELDcheck: links each HTTP call to theModel.fromJsonthat parses it and to the backend response model for that endpoint. Fails only for a non-null cast (j['id'] as String) the backend does not declare; anything the scan cannot prove required is aFIELD?review item. Dict-returning endpoints are skipped, never guessed. - Dart constants resolved (
'$v4/x'), trailing$path-style dynamic segments checked as a prefix (DYNAMIC). - FastAPI extractor: response models across files, inheritance,
List/Optional/X | None, return annotations,Field(alias=...); staticinclude_routerprefixes;backend.prefix_rulefor directory-derived mounting. - Loose
FIELD?= the backend never mentions the name anywhere (fields, attributes, kwargs, dict keys, strings). - Stop hook also lists
FIELDfindings;--no-endpoint-fieldsswitch.
Limits
Nested response fields are not flattened; request bodies are not compared per endpoint; no multi-level router chains; whether the app tolerates a missing key is only judged by a non-null cast.
Update
claude plugin marketplace update neo-plugins && claude plugin update fullstack-sync@neo-plugins, then restart Claude Code.