ReflexURL.path cannot be accessed as Var

[abulvenz]

Describe the bug
I wanted to remove the deprecation warning about router.path -> router.url.

To Reproduce

• Create empty app
• Place State.router.url.path
• See the error reflex.utils.exceptions.VarAttributeError: The State var reflex.state.State.router["url"] of type <class 'reflex.istate.data.ReflexURL'> has no attribute 'path' or may have been annotated wrongly.

Expected behavior
No error, because the deprecation message says, I should use url instead of path

• Python Version: 3.13.5
• Reflex Version: 0.8.?

[linear]

ENG-7249 ReflexURL.path cannot be accessed as Var

[adhami3310]

that's expected for now, I will get to it before 0.9

[benedikt-bartscher]

It's sad that the old router data is marked as deprecated, encouraging users to migrate, while the new one does not support all features

[adhami3310]

yea it was quite difficult getting all the features done in one PR, i will try to shackle the deprecation warnings in the future 👍

[benedikt-bartscher]

Maybe it would be nice (but probably not easy) to evaluate TYPE_CHECKING blocks in get_attribute_access_type by default. Or provide an alternative bool which is only True during reflex compile without affecting runtime behavior

[adhami3310]

well it wouldn't work anyways, because we are sending just a string to the frontend, it cannot access . fields

[benedikt-bartscher]

Yeah, you are right... We could add a serializer, but that would be inefficient. We could try to add some smart frontend helpers to manipulate the url. I guess the easiest and safest way is to serialize the single parts of the url and put them back together in the frontend if you want to access the full url. This way the splitting is always done in the backend and there should be no drift between how the frontend splits it

[benedikt-bartscher]

Btw, my hybrid_property draft would be nice to accomplish this without adding separate properties for frontend and backend: #3806