It would be helpful if the documentation for the table_columns parameter surfaced in API Client resources (like in post_files_csv, among others) specified that the array of hashes must be ordered. Since these are key:value pairs, I initially assumed that as with Python dictionaries the order would be irrelevant. It took me a while of puzzling over very confusing downstream errors before realizing I had to provide them in the same order as the columns of the table. Apparently arrays of hashes are always like this / this is common computer science knowledge, but I've never used hashes before and it was not intuitive.
As Manticore is working on surfacing table_columns in even more places, I suspect other people will run into this more in the future.
For reference, the current documentation looks like this:
It would be helpful if the documentation for the
table_columnsparameter surfaced in API Client resources (like inpost_files_csv, among others) specified that the array of hashes must be ordered. Since these are key:value pairs, I initially assumed that as with Python dictionaries the order would be irrelevant. It took me a while of puzzling over very confusing downstream errors before realizing I had to provide them in the same order as the columns of the table. Apparently arrays of hashes are always like this / this is common computer science knowledge, but I've never used hashes before and it was not intuitive.As Manticore is working on surfacing
table_columnsin even more places, I suspect other people will run into this more in the future.For reference, the current documentation looks like this:
