-
Notifications
You must be signed in to change notification settings - Fork 421
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
Merges master into minor #1805
Closed
Closed
Merges master into minor #1805
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reference values
can-simple-dom now exports a `default` only, so we need to update our code that's using it to refer to `default`.
That is not a can.view.Scope.Refs.
Now you don't have to use the .default property.
This makes it so that a renderer in the scope can initially be `null` (which will happen if using #references) and the partial renderer will recompute after the renderer is in the scope.
This enables the syntax: ```html <can-import from="other.stache!" #other="{value}"/> {{> other}} ```
Virtual DOM and place-my-order functionality
This updates can/view/import to set the `value` property on the can-import viewModel after the promise has resolved when used with can-tag. The reason this is needed is because when handing off control to a can.Component there will be a new viewModel created for that element. So we need to set the import value so that it can be used by the can-tag (or within the template as a reference value).
Allow importing a template and using as partial
Add example closer to relevant text
Make chapter code download more obvious.
Remove hyperlink to PlaceMyOrder.com, which is a DoneJS site.
Add a small section for can.fixture, and a UL overview of the deps section
Travis new infrastructure
Instead of: ```js var node = parent.childNodes[0]; ``` we always need to do: ```js var node = parent.childNodes.item(0); ``` To support the virtual DOM environment.
To make it possible for can to be loaded in a Web Worker we need to set can.global to the correct object, `self` and use it in can/util/vdom.
Allow loading in a web worker
Live-list diffing
Use NodeList.prototype.item to get a childNode
Revert "Use [.] to represent a template's viewModel"
This fixes CanJS so that it can be ran in a Web Worker context. The key changes: * Added a `can.isWebWorker` so that we can call `setState()` in can.route. * can.route looks for `can.route.location` first when updating the state, because in Worker Rendering we set a can.route.location.
Allow CanJS to run in a web worker.
This shims window.history when operating in a vdom environment so that can/route/pushstate will load. It's up to other libraries to provide the functionality of pushState/replaceState.
Shim window.history when in vdom environment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For #1650 cc @daffl