How to give custom parsing higher precedence or change string “definition”
I'm trying to change parsing of JSON files/code so that it recognizes that not everything under double quotes is really a string (JSON "by the book" puts everything into strings). I'm using excerpt from a schema since it has additional complexity. For example in
"title": {
"type": "string"
}
"title", "type" and "string" are actually different kinds of symbols.
I can get it to distinguish these with regexp but the built-in definition of string takes precedence for everything inside double quotes.
So I need either a way push the precedence of custom parsers up or a way to redefine string (so that it becomes context aware). Doesn't have to be via UI - hacking a config file is perfectly acceptable :-)
source-insight
add a comment |
I'm trying to change parsing of JSON files/code so that it recognizes that not everything under double quotes is really a string (JSON "by the book" puts everything into strings). I'm using excerpt from a schema since it has additional complexity. For example in
"title": {
"type": "string"
}
"title", "type" and "string" are actually different kinds of symbols.
I can get it to distinguish these with regexp but the built-in definition of string takes precedence for everything inside double quotes.
So I need either a way push the precedence of custom parsers up or a way to redefine string (so that it becomes context aware). Doesn't have to be via UI - hacking a config file is perfectly acceptable :-)
source-insight
add a comment |
I'm trying to change parsing of JSON files/code so that it recognizes that not everything under double quotes is really a string (JSON "by the book" puts everything into strings). I'm using excerpt from a schema since it has additional complexity. For example in
"title": {
"type": "string"
}
"title", "type" and "string" are actually different kinds of symbols.
I can get it to distinguish these with regexp but the built-in definition of string takes precedence for everything inside double quotes.
So I need either a way push the precedence of custom parsers up or a way to redefine string (so that it becomes context aware). Doesn't have to be via UI - hacking a config file is perfectly acceptable :-)
source-insight
I'm trying to change parsing of JSON files/code so that it recognizes that not everything under double quotes is really a string (JSON "by the book" puts everything into strings). I'm using excerpt from a schema since it has additional complexity. For example in
"title": {
"type": "string"
}
"title", "type" and "string" are actually different kinds of symbols.
I can get it to distinguish these with regexp but the built-in definition of string takes precedence for everything inside double quotes.
So I need either a way push the precedence of custom parsers up or a way to redefine string (so that it becomes context aware). Doesn't have to be via UI - hacking a config file is perfectly acceptable :-)
source-insight
source-insight
asked Nov 13 at 3:52
ZXX
4,1132031
4,1132031
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53273524%2fhow-to-give-custom-parsing-higher-precedence-or-change-string-definition%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53273524%2fhow-to-give-custom-parsing-higher-precedence-or-change-string-definition%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown