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

Migration Guide: Document that can-map no longer creates a custom can-list #34

Open
chasenlehara opened this issue Mar 16, 2017 · 0 comments
Labels

Comments

@chasenlehara
Copy link
Member

chasenlehara commented Mar 16, 2017

@ccummings commented on Wed Mar 15 2017

In 2.3, creating a custom can.Map would also create a custom can.List whose static Map property was the custom Map. For example:

const MyMap = can.Map.extend({
  myHelper() {
  }
});

//MyMap.List can now be used elsewhere

In 3.0 this was removed.

If the removal is permanent, it should be added to the migration guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant