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

New Insert Code Hints with Tab Preference#6984

Merged
RaymondLim merged 2 commits intomasterfrom
tom/codehints-on-tab
Mar 4, 2014
Merged

New Insert Code Hints with Tab Preference#6984
RaymondLim merged 2 commits intomasterfrom
tom/codehints-on-tab

Conversation

@TomMalbran
Copy link
Copy Markdown
Contributor

Just added this new Preference using the existing code. @iwehrman extension should still work.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I noticed that this isn't needed anymore with the latest API change.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nice catch on this.

@TomMalbran
Copy link
Copy Markdown
Contributor Author

@peterflynn @RaymondLim Ready for re-review/merge :)

@RaymondLim
Copy link
Copy Markdown
Contributor

Sure, I'll merge in a few minutes after I verify with your branch.

@TomMalbran
Copy link
Copy Markdown
Contributor Author

Cool, thanks

RaymondLim added a commit that referenced this pull request Mar 4, 2014
New Insert Code Hints with Tab Preference
@RaymondLim RaymondLim merged commit 93f22d8 into master Mar 4, 2014
@RaymondLim RaymondLim deleted the tom/codehints-on-tab branch March 4, 2014 07:15
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@TomMalbran @RaymondLim Note: APIs should be deprecated first, and not removed for a few releases to give extension authors time to fix or remove their extensions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

See #6984 (comment):

Or it might be reasonable to just deprecate or remove this API. Afaik there's only one extension that uses it, and it would be basically obsoleted by the new preference anyway.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Well, that 1 extension wasn't updated. If it was communicated somewhere this user didn't read or understand it. Also some people write extension that are only used privately (i.e. they are not posted to public exchange), so we can't know how many extensions use the API call.

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.

5 participants