Skip to content

remove_cv in writeObjects and readObjects - #1752

Open
AnyOldName3 wants to merge 1 commit into
vsg-dev:masterfrom
AnyOldName3:dont-serialise-constness
Open

AnyOldName3 wants to merge 1 commit into
vsg-dev:masterfrom
AnyOldName3:dont-serialise-constness

Conversation

@AnyOldName3

Copy link
Copy Markdown
Contributor

Pull Request Template

Description

There's no reason const values shouldn't be serialisable, but matchPropertyName can't handle type names with spaces in, so we can't read them back if we write the const prefix or expect it to be in the name we've read.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Arguably either a bugfix (it stops something someone might expect to be serialisable from failing to deserialise) or a feature (it makes something deserialisable that wasn't before)

How Has This Been Tested?

I've serialised and deserialised some const values that errored out without this change.

There's no reason const values shouldn't be serialisable, but matchPropertyName can't handle type names with spaces in, so we can't read them back if we write the `const ` prefix or expect it to be in the name we've read.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant