RayPals/Claro
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

test: cover chained object field assignments

Browse Source
This commit is contained in:
Hermes Agent
2026-09-06 16:09:10 +00:00
parent 9b93bea7e0
commit 75b2152f23
4 changed files with 27 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ADVANCED_STATIC_TYPING.md
+15
View File
@@ -74,6 +74,21 @@ Type mismatch for field alias.score: expected NUMBER, but this value looks like
This is intentionally limited to simple aliases. Broader object-flow analysis through branches, loops, and complex expressions remains planned.
The same field-assignment check follows a second simple alias. This lets a learner use a more descriptive name without losing the class field type:
```claro
SET backup alias
SET backup.score "ten"
```
Output:
```text
Type mismatch for field backup.score: expected NUMBER, but this value looks like TEXT.
```
This remains limited to direct assignments through simple alias chains; control-flow and complex object-flow analysis are still planned.
`CHECK TYPE` also follows simple aliases for direct field metadata checks. This includes a second alias, so learners can give an object a more descriptive local name without losing the class field information:
```claro