Sheath rule
native-unknown-navigate-transition
when an unknown modifier has a close supported spelling
#Why
An unknown @navigate modifier is ignored. Navigation still occurs, but the
requested transition or navigation behavior does not.
#Examples
#Bad
{{-- slideFromRigt is unknown, so the transition is ignored. --}}
<native:button @navigate.slideFromRigt="/articles/1">
Open article
</native:button>
#Good
{{-- slideFromRight is a supported transition. --}}
<native:button @navigate.slideFromRight="/articles/1">
Open article
</native:button>
Navigation types such as back, replace, and exitToWeb are also accepted.
#Supported Transitions
Transition names follow the installed NativePHP version when it exposes its
supported set. The bundled fallback includes fade, the slide variants,
fadeFromBottom, scaleFromCenter, parallaxPush, and none.
Only the final effective navigation assignment is checked. An earlier invalid
directive replaced by a later _navigate value is not reported.
#Syntax
Navigate assignments must use single or double quotes without whitespace
around =. Forms that NativePHP cannot consume are reported:
<native:button @navigate = "/articles">Articles</native:button>
#Options
All NativePHP rules accept nativeViewPaths. The default is
['views/native/']. See Native View Detection
for path configuration.
#See Also
Related rules validate other directive surfaces:
- native-unsupported-event: Check event support on the target element
- native-callback-exists: Validate callback methods and arguments