Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v4 Insert variable at cursor position (for script editor) #3959

Closed
MarkSiedle opened this issue Nov 23, 2017 · 3 comments
Closed

v4 Insert variable at cursor position (for script editor) #3959

MarkSiedle opened this issue Nov 23, 2017 · 3 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@MarkSiedle
Copy link

MarkSiedle commented Nov 23, 2017

When editing a script and using the "add variable" action to insert a variable into the script, it is appending the variable to the end of the content, instead of inserting the variable at the cursor position. This used to insert at the cursor position for v3 in the script editor, so this is a new bug introduced in v4.

Note: This should also replace selections. I.e. If I select text and insert variable, that selected text should be replaced (just how old variable insert worked).

Source: https://help.octopusdeploy.com/discussions/problems/64091

@MarkSiedle MarkSiedle added the kind/bug This issue represents a verified problem we are committed to solving label Nov 23, 2017
@MarkSiedle MarkSiedle self-assigned this Nov 23, 2017
@MarkSiedle
Copy link
Author

@johnsimons johnsimons assigned johnsimons and unassigned MarkSiedle Nov 24, 2017
@johnsimons johnsimons added this to the 4.0.7 milestone Nov 24, 2017
@octoreleasebot
Copy link

Release Note: Code editor in 4.0 now inserts variable at cursor position

@lock
Copy link

lock bot commented Nov 24, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants