Fix a bad "type" in the complex key example. #229
Merged
Conversation
This file contains hidden or 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
I must have been tired when I made that... looks like it's my fault the demo is broken. Also, unquoted brackets in form declarations do work because both Angular and ObjectPath try to guess what is meant; however, that really isn't best practice and shouldn't be in the example.
Dervisevic added a commit that referenced this pull request Jan 25, 2015
Fix a bad "type" in the complex key example.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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.
I must have been tired when I made that... it looks like it's my fault the demo is broken on that page.
Also, the unquoted brackets in form declarations do work because both Angular and ObjectPath try to guess what is meant; however, that really isn't best practice and shouldn't be in the example.