Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Solved starter bug: Issue #1976 - Rename on Second Click #2356

Merged
merged 3 commits into from
Dec 17, 2012
Merged

Solved starter bug: Issue #1976 - Rename on Second Click #2356

merged 3 commits into from
Dec 17, 2012

Conversation

gabriellcardoso
Copy link
Contributor

It's my first attempt to solve a bug in a open source project. Although I have read all wiki, I may do something wrong. So please let me know if I did something wrong.

@ghost ghost assigned redmunds Dec 14, 2012
_selectCurrentDocument();
result = (new $.Deferred()).resolve().promise();
if (rename) {
result = CommandManager.execute(Commands.FILE_RENAME);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gabriel,

Thanks for submitting contributions to Brackets, but this code doesn't belong in the openAndSelectDocument() function. This will change the entire meaning of the function.

In general, the code should work like this: when a file is clicked in either the working set list or the project tree, and it is not already selected, the openAndSelectDocument() function should be called. If the file is already selected, then code should be called to rename it.

Also note that your code currently only works on second click in the working set, but I think it should also work in the project tree.

Not sure how familiar you are with github, but after you have updated your code, you don't need to submit a new pull request -- just push you're changes to this same branch and they will show up here. Also, add a comment to the pull request to say you are "ready for another review" so I will get notified with an e-mail.

Thanks,
Randy

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Randy,

Be welcome. It's really a pleasure contribute to Brackets. I'm sorry that i changed it context, but I was confused because of that call of openAndSelectDocument() at drop function on WorkspaceSetView module. I thought that it was only to a drag and drop event. Now, I fixed it.

I just think it's a bit confusing have a rename second click event on project tree, it already have a double click event, that is add the selected file to Workspace Set. I can implement it to project tree, but how I said to me it's a bit confusing have two effects and a same gesture to project tree. Let me know if you decide that is better implement it to project tree too.

I'm ready for another review.

Thanks,
Gabriel

Remove it from FileViewController.openAndSelectDocument method and add
it to WorkingSetView drop event.
CommandManager.execute(Commands.FILE_RENAME);
} else {
FileViewController.openAndSelectDocument($listItem.data(_FILE_KEY).fullPath, FileViewController.WORKING_SET_VIEW);
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indenting is not correct. Brackets uses indenting of 4 spaces.

Be sure that View > Enable JSLint is turned on for Brackets code -- I think that would have caught this problem.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't point in JSLint if I didn't mixed both in a single line and it happened because I forgot to change between projects.

That's is a issue in Brackets, it doesn't keep your indenting by project. I commited again solving this indenting problem.

@redmunds
Copy link
Contributor

This is much better. Just need to fix the indenting.

I see your point about single-click in the project tree -- it would only make sense if the file is already in the Working Set. We can add that later if desired.

@redmunds
Copy link
Contributor

Looks good. Merging.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants