Force custom translation if any before parse checks #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Force the custom translation defined by the user before perfoming other checks.
There are some problems when the user tries to custom translate an C# Array to a javascript type.
I've trying to custom translate
byte[]
tostring
, but it ended up translating it tostring[]
.I had similar problems trying to translate
Model[]
toAnotherModel[]
.My config-file.json at "customTypeTranslations" was sometinh like this:
In this case, I'm assuming that the dev knows what he's doing when he, by adding a custom translation, chooses to translate, for example, and array of
Model
to an array ofAnotherModel
.Closes #33