Avoiding use of Object.setPrototypeOf

#90

v4.1.1

Removes the stringified regex from the warning message #85

v4.1.0

Remove can-util as dependency 51d39f5

v4.0.1

Clean up markdown sample code #82

Automount tags

#65

v3.2.5

Clean up the docs #70

v3.2.4

Docs updates: #68 #69

Fixed a bug, updated the docs, added cycle detection

• Add a cycle detection script to test process #63
• Don’t warn about registered native custom elements #64
• Update docs with new @parent & @collection #66

v3.2.2...v3.2.3

v3.2.2

• Fix bug preventing registered callback from being returned #61

v3.2.1...v3.2.2

Improved development warnings, better tag method response

Improved Tag response

• PR: #59
• Issue: canjs/can-view-import#2

When attempting to retrieve the handle for a given tag that has not been registered, like tag('hello-world'), the tag method would return a noop. In some cases, this made it difficult to determine if a tag exists or not since a tag that exists returns a function as well.

Now, can-view-callbacks exports a default noop function, defaultCallback so a comparison can be made to the result of the tag method.

import callbacks from 'can-view-callbacks';
const tagHandler = tag('hello-world');
const tagNotRegistered = callbacks.defaultCallback === tagHandler;

Improved development warnings

• PR: #58
• Issue: #57

A custom element attribute must be registered before it is rendered on an element. Previously, rendering an element with a custom attribute would not log a warning. A warning was added with a reminder that the attribute must be defined before it is used.