The redirect_to action has an action attribute which is being passed to Turbo.visit(..., { action }) to control the Turbo visit behaviour.

But the action attribute name is clashing with the <turbo-stream> element, since it's using the action attribute for determining the stream action to execute.

We should rename the attribute for the redirect_to action to either action_name or turbo_action.

This Pull Request deprecates the invoke stream action. If you'd like to continue using it you should use the successor library (@turbo-boost/streams) instead.

TurboPower will still register a stubbed out invoke stream action if the action wasn't registered yet, so you get a deprecation warning in the browser console.

This Pull Request adds a typecast util function in order to convert any string value to its typecast representation.

Due to the fact that HTML attributes are always strings we have to do the conversion.

Action signature:

turbo_stream.reset_form(target, **attributes)

Reference:

• https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormElement/reset
• https://twitter.com/excid3/status/1601285720106094592

Maybe it would makes sense to extract all the Turbo related actions into a src/actions/turbo.ts file.

For now this is:

• redirect_to (or a potential turbo_visit)
• turbo_clear_cache

The Turbolinks cases in all actions were taken over from the CableReady operations.

But technically Turbolinks isn't really compatible with TurboPower since you actually need to have Turbo installed in your app if you want to use Custom Turbo Stream Actions.

Action signature:

turbo_stream.turbo_clear_cache()

Action content:

Turbo.cache.clear()

Reference: https://turbo.hotwired.dev/reference/drive#turbo.cache.clear

Hi marcoroth/turbo_power!

This is a one-off automatically generated pull request from LGTM.com :robot:. You might have heard that we’ve integrated LGTM’s underlying CodeQL analysis engine natively into GitHub. The result is GitHub code scanning!

With LGTM fully integrated into code scanning, we are focused on improving CodeQL within the native GitHub code scanning experience. In order to take advantage of current and future improvements to our analysis capabilities, we suggest you enable code scanning on your repository. Please take a look at our blog post for more information.

This pull request enables code scanning by adding an auto-generated codeql.yml workflow file for GitHub Actions to your repository — take a look! We tested it before opening this pull request, so all should be working :heavy_check_mark:. In fact, you might already have seen some alerts appear on this pull request!

Where needed and if possible, we’ve adjusted the configuration to the needs of your particular repository. But of course, you should feel free to tweak it further! Check this page for detailed documentation.

Questions? Check out the FAQ below!

FAQ

closes #6

This PR adds the set_turbo_frame_src operation.
I created a new src/actions/turbo_frames.ts file for turbo_frame operations. The reason for this is that in the future there might be more custom TurboFrame operations and it would be nice to have them all in one place.

Another way would have been to implement the set_turbo_frame_src operation in existing files like src/actions/dom.ts or src/actions/attributes.ts.

Would love to hear what you think about it

Action signature:

turbo_stream.console_table(data, columns = nil, **attributes)

Reference: https://developer.mozilla.org/en-US/docs/Web/API/Console/table

Action signature:

turbo_stream.console_log(message, level = :log, **attributes)

Reference: https://developer.mozilla.org/en-US/docs/Web/API/Console/log

Not sure how useful this is, but it might be interesting to have an action to set a window.onbeforeunload callback. This can be handy to set from the server-side when you are sending down some data which is not persisted yet. And with this you would get a warning when you attempt to close the window/tab. Like:

The example above can be achieved with this snippet:

window.onbeforeunload = function() {
  return true;
}

Obviously we would also need an action to clear the event-listener again.

Something like:

import * as Turbo from '@hotwired/turbo'
import TurboPower, { AttributeActions, BrowserActions } from 'turbo_power'

TurboPower.initialize(Turbo.StreamActions, [AttributeActions, BrowserActions])

Add an action/multiple actions for controlling the Turbo progress bar

Turbo.navigator.adapter.progressBar.setValue(value)
Turbo.navigator.adapter.progressBar.show()
Turbo.navigator.adapter.progressBar.hide()

Action signature:

turbo_stream.turbo_visit(location, action = "advance", **attributes)

Action content:

Turbo.visit(location)
Turbo.visit(location, { action: turbo_action })

Check out the existing redirect_to action, which technically already covers the use-case for this action.

Reference: https://turbo.hotwired.dev/reference/drive#turbo.visit

Currently you need to pass turbo="true" to the <turbo-stream> element in order that is uses Turbo.visit():

<turbo-stream turbo="true" url="http://localhost:3000/" action="redirect_to"><template></template></turbo-stream>

It should use Turbo.visit() by default unless turbo="false" gets explicitly passed to the stream element.

The action already accounts for when Turbo/Turbolinks is not installed in the application and will fallback to window.location.href = url

https://github.com/marcoroth/turbo_power/blob/623a6f5b11608073ac36880bd1f0cc4745a52e56/src/actions/browser.ts#L17

Thanks for the great lib!

It would be nice to have a shortcut to modify Turbo.navigator.history. I find it an essential action since the Back button is not doing what is expected when the browser history is modified without touching Turbo.navigator.history. As a workaround, the invoke action can be used at the moment.

More on the issue: https://discuss.hotwired.dev/t/back-button-not-working/3012

P.S. I'd really love to help but I'm not very familiar with Typescript yet :/