Code editor issue follow-up & improvement

Feature Request Node Improvement
1

Following up on Broken code editor on Windows/Chrome - please fix - #9

Creating a new topic as the previous one was automatically closed before I could even reply :sweat_smile:

Hey @Wasay-Gumloop & @Luis thanks for the good news :slight_smile:

I just tested and can confirm that the cursor discrepancy bug is now fixed on Windows/Chrome - and no need to reload the Run Code nodes. Also confirmed with the Custom Node code editor. You just made my day :tada:

There’s still one minor issue left - one “ghost” trailing space character remains visible when selecting multiple lines as you can see below :

{09F4FD18-1DB5-4E63-AE45-6946CB4FCBA5}
{09F4FD18-1DB5-4E63-AE45-6946CB4FCBA5}616×301 19.4 KB

Next, as mentioned in my original post - please prioritize improving the Gumloop code editor UX & workflow. As a first step, we should be able to expand the Run Code editor.

Then we could go even further, by enabling the user to export/import .py files to edit them in the user IDE of choice (so we could use our favorite AI).

This is really important as this is where a lot of Gumloop power resides. Let me know if you want to discuss the topic further and if you need me for testing.

Keep it up, cheers :rocket:

Romain

2

Hey @cdromain – Thanks so much for retesting and confirming the cursor discrepancy fix!

On the ghost trailing space when selecting multiple lines: could you share a workflow link where you can reproduce this? That will help us zero in and ship a fix.

On the code editor UX requests: totally hear you. This is a bit of a longer-term improvement, but it’s on our roadmap. We’ll keep you posted as we scope timelines, and we’d love to pull you in for testing.

Thanks again, Romain. This is exactly the kind of feedback that helps us make Gumloop better :slight_smile:

1 Like
3

Hey @Wasay-Gumloop

Thanks for your reply.

Here’s a test workflow showcasing the ghost trailing space : https://www.gumloop.com/pipeline?workbook_id=wnpVz3kHMZkPfXvwifjJYs

{F0BD952C-6520-4BAC-B5DA-BE6416D89E65}
{F0BD952C-6520-4BAC-B5DA-BE6416D89E65}831×295 21.2 KB

Great news about the code editor UX improvement being on the roadmap, looking forward to it and you can definitely count on me for input & testing :rocket:

This morning I witnessed some kind of regression as the Windows broken behavior (cursor discrepancy) was back :

{963D51EE-7446-4F41-945A-32D04EB5242D}
{963D51EE-7446-4F41-945A-32D04EB5242D}774×316 16.8 KB

And then the issue disappeared by magic switching to other workflows. Will keep you posted in case the problem reappears.

All the best,

Romain

4

Hey @cdromain, thanks for flagging this! I was able to reproduce the ghost trailing space issue and have created a ticket so the team can work on it. I’ll let you know once that’s resolved.

If you notice the cursor discrepancy again, feel free to capture it using this link: https://recorder.jam.dev/UjTXZZn so we can track down what’s causing it.

We really appreciate you sharing detailed feedback like this. Keep it coming! :rocket:

1 Like
5

Hey @Rithen_Gumloop, thanks for confirming and creating a ticket.

Submitted a quick recording showing the issue - on my Windows Chrome it’s as simple and systematic as starting from an empty workflow and adding a Run Code node, before selecting all code with CTRL + A.

I’ll keep it coming but hopefully I won’t have to (too often) :grinning_face_with_smiling_eyes: I’d rather focus on features suggestions to help improving Gumloop :rocket:

Cheers,

Romain

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.