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.

Sign up for GitHub

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

Jump to bottom

array_fmtstrings doesn't actually default to 0/#-1 for omitted items #81

Closed
charlesreiss opened this issue Mar 4, 2017 · 1 comment
Closed

array_fmtstrings doesn't actually default to 0/#-1 for omitted items #81

charlesreiss opened this issue Mar 4, 2017 · 1 comment

Comments

@charlesreiss
Copy link
Contributor

array_fmtstrings's documentation claims that it defaults to 0 if a value is not an input dictionary, but it doesn't do this for floats or ints or dbrefs. (The code defaults to a null string, which then fails a typecheck.)
wyld-sw added a commit that referenced this issue Apr 14, 2017
@wyld-sw
Defaulted omitted items to type-appropriate values in ARRAY_FMTSTRING…
80de55a 
…S. (#81)
@wyld-sw
Copy link
Member

wyld-sw commented Apr 14, 2017

Should be fixed.

@wyld-sw wyld-sw closed this as completed Apr 14, 2017
wyld-sw added a commit that referenced this issue Sep 16, 2017
@wyld-sw
Defaulted omitted items to type-appropriate values in ARRAY_FMTSTRING…
84ea7e2 
…S. (#81)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@charlesreiss @wyld-sw