Vlad

+1 It is unfortunate that it's too slow to decode/encode.

I believe this issue is the same as #1115. `fzf` starts in fullscreen mode by default and that's causing Warp to "freak out". Until this is fixed, a temporary workaround...

Thanks for the plugin. Any desire to implement pull quotes on both sides?

@YamiOdymel, this feature request goes beyond simple error handling is more along the lines of React's [Error Boundaries](https://reactjs.org/docs/error-boundaries.html).

> Reopening because GV hasn't been released with this yet. @rafaehlers this was released in v2.21: `* Support for Gravity Flow's "Workflow User" and "Workflow Multi-User" fields inside the Search...

@omarkasem, while this PR works, the View's field `number_format` option is no longer respected (see the failing test). When unchecked, all numbers are now displayed with the thousands separator (`,`...

@omarkasem, I appreciate your [October 11 comment](https://github.com/GravityKit/GravityView/pull/1879#issuecomment-1757119144). However, I'm afraid I still have concerns about the number formatting issue that this PR was supposed to address. When the number field...

@omarkasem, when you configure the `Number` form field to use the `9.999,99` format, GF will display the number formatted exactly like that. GV (this feature branch), on the other hand,...

@omarkasem, could you please provide a status update? If this is implemented, please make sure that all tests pass and update the project status to `Blocked: Needs Review`.

> @mrcasual It's working but the tests needs to be changed as I mentioned before [here](https://github.com/GravityKit/GravityView/pull/1879#issuecomment-1757119144) > > So should I work on the tests change? If so I will...