-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat: update rename functionality #141
base: master
Are you sure you want to change the base?
feat: update rename functionality #141
Conversation
lib/views/dialog.ts
Outdated
@@ -0,0 +1,37 @@ | |||
import { TextEditor } from "atom" | |||
|
|||
export default class Dialog { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually created a dialog view for some other atom packages https://github.com/UziTech/atom-modal-views. Do we want to use that instead of creating our own?
/cc @aminya
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually created a dialog view for some other atom packages UziTech/atom-modal-views. Do we want to use that instead of creating our own?
That sounds like a good plan! I love reusing code.
The last time I checked the intentions package was quite buggy. For example, it disabled selecting the text, or the underlines were longer than what they should be. I thought @steelbrain had stopped supporting it. So, if we need to add a new package for renaming I am ok with it. |
I got access to the intentions package. We should fix these issues before merging this PR. |
Hi, any updates on this functionality? Will this be merged in the near future? Thank you all from atom-community for your work! |
Hi,
To my understanding, the current rename implementation doesn't work anymore.
I'm even wondering if it worked at some point because of the comment that @lexi-lambda made in the PR description: atom/atom-languageclient#270
Anyways, it seemed to rely on the archived atom-ide-ui...
So here's a draft PR to suggest two different implementations:
Both approaches have advantages and drawbacks, eg.
Commands and context menu
Intentions