Remove use of can-connect/can/tag/ from guides
See original GitHub issueThis might be called out somewhere else, but we should remove this kind of thing from the guides since this is not how 99% of applications will handle retrieving data from models:
<restaurant-model get="{ _id=slug }">
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Migrating to CanJS 6 | upgrade | Guides - CanJS
This guide walks you through the process to upgrade a 5.x app to CanJS 6.x. ... beforeremove event removed; can-connect/can/tag moved to an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think this is a valid way to retrieve data, why do you dislike it?
Ah, we can close this for #515, but I still think this is worth it. This will be a big improvement to the guides and the initial user experience of DoneJS. I’ve seen way too much confusion around connect/tags. I’d rather have this fix over the performance improvements.