Throw and exception when inferring from JSON Schema and the resulting Concerto is about to include reserved keywords

[stefanblaginov]

Context

Concerto has a number of reserved words that cannot be used in a valid Concerto file. Currently the JSON Schema inference code lets us create a Concerto file with these reserved words.

That should not be the case and and error must be thrown that an invalid file is about be created.

[kailash360]

@stefanblaginov @sanketshevkar

Can I take up this issue?

[sanketshevkar]

Yep sure!

[kailash360]

Since we already have the list of available reserved words, we can check if the current field is a part of the list or not. However, I have small doubt if we should check for these words without the $ symbol as well. For example, if $timestamp is a reserved word then user obviously cannot use $timestamp in the concerto file, but whether the user can use timestamp field or not.

@sanketshevkar @dselman can you please confirm on this?

[sanketshevkar]

Since we already have the list of available reserved words, we can check if the current field is a part of the list or not. However, I have small doubt if we should check for these words without the $ symbol as well. For example, if $timestamp is a reserved word then user obviously cannot use $timestamp in the concerto file, but whether the user can use timestamp field or not.

I believe $ is added so as to let users know its a reserved keyword. We would like to name our variables like $class or __prototype__ (in JS), so that someone won't accidently use them. @dselman is that correct?