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
Use case: To use htmlizer on server-side to do a render, but preserve any event binding for client-side so that it can be used with knockoutjs.
However, the use case I only anticipated is that the same template would be used on client and server side, and so currently data-bind attribute is completely stripped off by htmlizer.
Note: There could be a second use case, where user needs to do a partial render with htmlizer. To solve that, we'll need a separate attribute like data-htmlizer or something.
The text was updated successfully, but these errors were encountered:
Having an attribute like data-htmlizer can solve both use cases. It will be through a boolean config parameter named "noConflict" (default false). It will also not process any containerless statements that begin with "ko " prefix.
Use case: To use htmlizer on server-side to do a render, but preserve any event binding for client-side so that it can be used with knockoutjs.
However, the use case I only anticipated is that the same template would be used on client and server side, and so currently data-bind attribute is completely stripped off by htmlizer.
Note: There could be a second use case, where user needs to do a partial render with htmlizer. To solve that, we'll need a separate attribute like data-htmlizer or something.
The text was updated successfully, but these errors were encountered: