Skip to content

3 spaces as a tab-stop for XML blobs? #19

@hellt

Description

@hellt

Hi @pdellaert
I spotted an interesting thing. When you create some object which accepts XML Blobs (for instance VNF Metadata) you receive the blob back with 3 spaces used as a tab stop:

image

In CATS, after creation of any object we perform double-check operation which compares params pushed to VSD and ones we received back. This check failed for XML blob because of 4spaces vs 3 spaces
While comparing blobs might not be a good idea, still 3 spaces used as a tab stop seems a bit questionable =)

Metadata

Metadata

Assignees

Labels

backendIndicates an issue that is not in VSPK itself, but in the Nuage VSD environment

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions