Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does it work with model POJO attributes? #139

Closed
sbsurf opened this issue Feb 12, 2015 · 1 comment
Closed

Does it work with model POJO attributes? #139

sbsurf opened this issue Feb 12, 2015 · 1 comment

Comments

@sbsurf
Copy link

sbsurf commented Feb 12, 2015

I'm running into issues unit testing a model which has POJO attributes. E.g.:

export default DS.Model.extend({
  Collections: DS.hasMany('collection', {async: true}), 
  DisplayCompliance: DS.attr(), //POJO
  LastCachedTimestamp: DS.attr('string'),
  ResourceUri: DS.attr('string'),
  StandardFields: DS.attr(), //POJO
  CustomFields: DS.attr(), //POJO
  RentalCalendar: DS.attr() //POJO
});

In my test, using moduleForModel, the subject object doesn't seem to contain those attributes. Only datatyped ones.

Am I doing something wrong?

@rwjblue
Copy link
Member

rwjblue commented Oct 17, 2017

Sorry for letting this linger so long, this issue is quite out of date and likely the underlying problem has been fixed. Initial implementation of the new ember-qunit API (from emberjs/rfcs#232) has landed and will be included in 3.0.0 release soon.

Closing as I do not believe that this issue can be addressed in the current ember-qunit@2 API.

@rwjblue rwjblue closed this as completed Oct 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants