Open brettin opened 9 years ago
A client can create an upload without providing either an empty string or undef as the object name. Is this the intended behavior?
In t/client-tests/create_uploade_node.t
ok 8 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: String, metadata: HASH(0x339b178) ok 9 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: String, metadata: HASH(0x3305e78) ok 10 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: Genome, metadata: HASH(0x339b178) ok 11 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: Genome, metadata: HASH(0x3305e78) ok 12 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: Unspecified, metadata: HASH(0x339b178) ok 13 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: Unspecified, metadata: HASH(0x3305e78) ok 14 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: String, metadata: HASH(0x339b178) ok 15 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: String, metadata: HASH(0x3305e78) ok 16 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: Genome, metadata: HASH(0x339b178) ok 17 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: Genome, metadata: HASH(0x3305e78) ok 18 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: Unspecified, metadata: HASH(0x339b178) ok 19 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: , object type: Unspecified, metadata: HASH(0x3305e78) ok 20 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: my-name, object type: String, metadata: HASH(0x339b178) ok 21 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: my-name, object type: String, metadata: HASH(0x3305e78) ok 22 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: my-name, object type: Genome, metadata: HASH(0x339b178) ok 23 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: my-name, object type: Genome, metadata: HASH(0x3305e78) ok 24 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: my-name, object type: Unspecified, metadata: HASH(0x339b178) ok 25 - can create_upload_node with path: /brettin/brettin-c54ebe4b-4245-4e6d-ac5b-7e537d9a311a/, object name: my-name, object type: Unspecified, metadata: HASH(0x3305e78)
Also, metadata can be undef or an empty hash.
ok 32 - can create_upload_node with path: /brettin/brettin-d7bf3b2f-dbea-423d-96f6-9b29bca0df95/, object name: my-name, object type: Unspecified, metadata:
A client can create an upload without providing either an empty string or undef as the object name. Is this the intended behavior?
In t/client-tests/create_uploade_node.t