From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] json what to do
Date: Sun, 06 May 2018 07:45:33 -0400 [thread overview]
Message-ID: <20180406074533.eklhad@comcast.net> (raw)
I know almost nothing about json so bear with me.
Open your Bibles please to
https://www.ibm.com/us-en/
Don't browse, just look at the html.
,s/></>\n</g
To make it readable.
Ok, the last script in the head section
<script type="application/ld+json">
What is that? I'm sure it's there for a reason. We need to know what to do with it.
I gathered it up into a string and passed it to JSON.parse() in duktape and it parses just fine.
That returns the corresponding javascript object.
All good, but what am I suppose to do with this object?
If I just feed this string to JSON.parse, that object gets thrown away. It all gets thrown away.
Unless I store it somewhere, but where?
The script doesn't specify a variable for me to put it in.
Do I put it under some property under the script object?
Any help appreciated.
Karl Dahlke
next reply other threads:[~2018-05-06 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 11:45 Karl Dahlke [this message]
2018-05-06 12:22 ` Dominique Martinet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180406074533.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).