Get rid of `autogenerated` on `@content` #262

Closed
HugoGiraudel opened this Issue Oct 13, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@HugoGiraudel
Member

HugoGiraudel commented Oct 13, 2014

We now have autofill on items. @content should use this, rather than relying on default and being generated like this:

{
  autogenerated: true
}

From a user standpoint, it should be kind of like @deprecated. If there is no message, it has no description (well, "" actually). Else, it has a description.

@HugoGiraudel HugoGiraudel added this to the 2.0 milestone Oct 13, 2014

@FWeinb

This comment has been minimized.

Show comment
Hide comment
@FWeinb

FWeinb Oct 13, 2014

Member

So if @content is found we should just add "" than?

Member

FWeinb commented Oct 13, 2014

So if @content is found we should just add "" than?

@HugoGiraudel

This comment has been minimized.

Show comment
Hide comment
@HugoGiraudel

HugoGiraudel Oct 13, 2014

Member

Yeah. Exactly like @deprecated.

'use strict';

module.exports = {
  parse: function (text) {
    return text.trim();
  }
};
Member

HugoGiraudel commented Oct 13, 2014

Yeah. Exactly like @deprecated.

'use strict';

module.exports = {
  parse: function (text) {
    return text.trim();
  }
};
@FWeinb

This comment has been minimized.

Show comment
Hide comment
@FWeinb

FWeinb Oct 13, 2014

Member

Done in #261

Member

FWeinb commented Oct 13, 2014

Done in #261

@FWeinb FWeinb closed this Oct 13, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment