You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow variations on control flow and region token matches
Make the support for tag based languages more obvious for these cases
Right now, a match for <? if (condition) ?> would have to indicate its if token as <? if (including the space between ? and if and omitting the required element close ?>
This can be accomplished by adding a specific tag provider that activates on <? (or, generically, an appropriate language open token), consumes whitespace, provides an activation flag to the normal if handler, and returns control to the main scan - this will require some design
The text was updated successfully, but these errors were encountered:
<? if (condition) ?>
would have to indicate itsif
token as<? if
(including the space between?
andif
and omitting the required element close?>
<?
(or, generically, an appropriate language open token), consumes whitespace, provides an activation flag to the normalif
handler, and returns control to the main scan - this will require some designThe text was updated successfully, but these errors were encountered: