-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missing information from jsonfeed #80
Comments
Similarly, items parsed from jsonfeeds are missing a type='entry' property |
@jackjamieson2 Will fix this. It should be on the library side |
Great, I implemented a quick fix to the dev branch of yarns but I agree it
should be in the library
…On Wed, Jun 19, 2019 at 6:07 PM David Shanske ***@***.***> wrote:
@jackjamieson2 <https://github.com/jackjamieson2> Will fix this. It
should be on the library side
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#80?email_source=notifications&email_token=AC5U5R4XQIGBYVUEYJOT6FTP3KU2JA5CNFSM4HZMY342YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDNNMI#issuecomment-503764657>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC5U5RZUCVMD4L4TJSA7KQ3P3KU2JANCNFSM4HZMY34Q>
.
|
@jackjamieson2 If you look at the JSONfeed you cited, and all micro.blog jsonfeeds, no author property exists. I'll fix the other problem. |
Not every feed has an author provided. Not sure what Microsub expects if there isn't one provided. |
Ah, I thought that might have been a jsonfeed convention, but I didn't check the spec. Nonetheless, my inclination would be to interpret the feed Beyond that, it looks like there's discussion of using a I'm heading to sleep now so I'll check properly in the morning, but it looks like this is implemented in Monocle (in |
I would rather start providing a source property for everything than the alternative |
Makes sense. I think I’ll keep this workaround in Yarns temporarily, and
remove it if/when _source can be used more reliably.
…On Thu, Jun 20, 2019 at 1:06 PM David Shanske ***@***.***> wrote:
I would rather start providing a source property for everything than the
alternative
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#80?email_source=notifications&email_token=AC5U5R24ACHVAXCRWMOGL6DP3O2HRA5CNFSM4HZMY342YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGAZWI#issuecomment-504106201>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC5U5R6ZVNCIRGLR57RWQZLP3O2HRANCNFSM4HZMY34Q>
.
|
e.g. when I parse manton.org/feed.json, the feed author information is not added to items
Looks like this is because the author information is not stored as an h-card like with other feeds
It returns with the author information as properties at the beginning of the feed.
Yarns is expecting an author property as an h-card
Two ways to address this:
I can add a bit to Yarns to convert this
This could be addressed in Parse-This -- @dshanske, what do you think? I'm happy to handle it in Yarns but I expect this would be useful in other cases of Parse-This as well.
I'm going to implement it in Yarns itself in the meantime since it's pretty simple and I want jsonfeeds to work asap
The text was updated successfully, but these errors were encountered: