Custom setting-specific completions not available

Issue #147 resolved

Zoran Žunko created an issue 2015-10-28

For example , <customSetting>.getOrgDefaults() not showing in autocomplete.

Comments (8)

Scott Wells repo owner
- edited description
- changed component to Completion
- changed version to Unassigned
- changed title to Custom setting-specific completions not available
- 2015-10-28T13:59:52+00:00
Zoran Žunko reporter
The funny thing is that getInstance() is displayed.
- 2015-10-28T14:17:05+00:00
Scott Wells repo owner
Yeah, because custom settings are just SObjects, they aren't reported by the APIs with these methods at all. I'm augmenting them at OST generation time with additional methods like this. This is actually true of several other aspects of the OST such as the shared base Object class, making SObject stub classes extend SObject itself, etc. Looks like I just haven't included all the ones that should be available for custom settings.
- 2015-10-28T14:32:10+00:00
Scott Wells repo owner
I'll have this one fixed in the next build. All custom settings stub classes will have completions for both list and hierarchy custom setting methods because I don't have a way to distinguish during generation, but they will be available.
- 2015-10-29T15:38:05+00:00
Zoran Žunko reporter
Great thanks.
- 2015-10-29T15:41:41+00:00
Scott Wells repo owner
- changed version to 1.6.4.5
- assigned issue to
  
  Scott Wells
- 2015-10-30T19:29:24+00:00
Scott Wells repo owner
- changed version to 1.6.5.0
- 2015-11-02T15:52:23+00:00
Scott Wells repo owner
- changed status to resolved
Delivered in 1.6.5.0.
- 2015-11-02T16:17:56+00:00
Log in to comment