Can-define warning type vs Type

CanJS
1

Hi All,

I am converting an application we are developing from v3 to v4. It seems ok so far, but I am getting a warning that I don’t know how to fix. I have a property defined like

export default DefineMap.extend({
      loadingThings: {
        type: 'boolean',
        default: true
      },

I see a warning in the console like:

can-define: the definition for loadingThings on DefineMap uses a constructor for “type”. Did you mean “Type”?

I searched the forum, but didn’t find an answer. Looking at the docs, ‘type’ seems correct and if I use ‘Type’ it fails to load the page. Any ideas as to what am I doing wrong, if anything, or how to surpress the warning?

I’m using the following set of can packages:
can-3-4-compat@1.0.0
can-component@4.0.7
can-connect@2.0.4
can-construct@3.3.1
can-construct-super@3.1.4
can-define@2.2.3
can-define-backup@1.0.0
can-route@4.1.1
can-route-pushstate@4.0.4
can-set@1.5.2
can-stache@4.3.3
can-stache-converters@4.0.2
can-stache-route-helpers@0.1.4
can-validate-validatejs@0.1.3
can-view-import@4.0.2

Cheers
Rob

2

@robfoweraker I don’t think this is anything you’re doing wrong. It looks like a bug in the warning caused by some recent changes.

Can you submit an issue here: https://github.com/canjs/can-define/issues?

3

Thanks, Done Issue #331

1 Like
4

fixed. Thanks for reporting.

1 Like