The gofeed library is a robust feed parser that supports parsing both RSS, Atom and JSON feeds. The library provides a universal gofeed.Parser that will parse and convert all feed types into a hybrid gofeed.Feed model. You also have the option of utilizing the feed specific atom.Parser or rss.Parser or json.Parser parsers which generate atom. Feed , rss.Feed and json.Feed respectively.
The gofeed library provides support for parsing several popular predefined extensions into ready-made structs, including Dublin Core and Apple’s iTunes.
It parses all other feed extensions in a generic way (see the Extensions section for more details).
Invalid Feeds
A best-effort attempt is made at parsing broken and invalid XML feeds. Currently, gofeed can succesfully parse feeds with the following issues:
Unescaped/Naked Markup in feed elements
Undeclared namespace prefixes
Missing closing tags on certain elements
Illegal tags within feed elements without namespace prefixes
Missing "required" elements as specified by the respective feed specs.
Incorrect date formats
Overview
The gofeed library is comprised of a universal feed parser and several feed specific parsers. Which one you choose depends entirely on your usecase. If you will be handling rss, atom and json feeds then it makes sense to use the gofeed. Parser . If you know ahead of time that you will only be parsing one feed type then it would make sense to use rss.Parser or atom.Parser or json. Parser .
Universal Feed Parser
The universal gofeed.Parser works in 3 stages: detection, parsing and translation. It first detects the feed type that it is currently parsing. Then it uses a feed specific parser to parse the feed into its true representation which will be either a rss.Feed or atom.Feed or json. Feed . These models cover every field possible for their respective feed types. Finally, they are translated into a gofeed.Feed model that is a hybrid of all feed types. Performing the universal feed parsing in these 3 stages allows for more flexibility and keeps the code base more maintainable by separating RSS, Atom and Json parsing into seperate packages.
The translation step is done by anything which adheres to the gofeed.Translator interface. The DefaultRSSTranslator , DefaultAtomTranslator , DefaultJSONTranslator are used behind the scenes when you use the gofeed.Parser with its default settings. You can see how they translate fields from atom.Feed or rss.Feedjson. Feed to the universal gofeed.Feed struct in the Default Mappings section. However, should you disagree with the way certain fields are translated you can easily supply your own gofeed.Translator and override this behavior. See the Advanced Usage section for an example how to do this.
Feed Specific Parsers
The gofeed library provides two feed specific parsers: atom. Parser , rss.Parser and json. Parser . If the hybrid gofeed.Feed model that the universal gofeed.Parser produces does not contain a field from the atom.Feed or rss.Feed or json.Feed model that you require, it might be beneficial to use the feed specific parsers. When using the atom.Parser or rss.Parser or json.Parser directly, you can access all of fields found in the atom. Feed , rss.Feed and json.Feed models. It is also marginally faster because you are able to skip the translation step.
Basic Usage
Universal Feed Parser
The most common usage scenario will be to use gofeed.Parser to parse an arbitrary RSS or Atom or JSON feed into the hybrid gofeed.Feed model. This hybrid model allows you to treat RSS, Atom and JSON feeds the same.
The mappings and precedence order that are outlined in the Default Mappings section are provided by the following two structs: DefaultRSSTranslator , DefaultAtomTranslator and DefaultJSONTranslator . If you have fields that you think should have a different precedence, or if you want to make a translator that is aware of an unsupported extension you can do this by specifying your own RSS or Atom or JSON translator when using the gofeed. Parser .
Here is a simple example of creating a custom Translator that makes the /rss/channel/itunes:author field have a higher precedence than the /rss/channel/managingEditor field in RSS feeds. We will wrap the existing DefaultRSSTranslator since we only want to change the behavior for a single field.
First we must define a custom translator:
import (
"fmt""github.com/mmcdole/gofeed""github.com/mmcdole/gofeed/rss"
)
typeMyCustomTranslatorstruct {
defaultTranslator*gofeed.DefaultRSSTranslator
}
funcNewMyCustomTranslator() *MyCustomTranslator {
t:=&MyCustomTranslator{}
// We create a DefaultRSSTranslator internally so we can wrap its Translate// call since we only want to modify the precedence for a single field.t.defaultTranslator=&gofeed.DefaultRSSTranslator{}
returnt
}
func (ct*MyCustomTranslator) Translate(feedinterface{}) (*gofeed.Feed, error) {
rss, found:=feed.(*rss.Feed)
if!found {
returnnil, fmt.Errorf("Feed did not match expected type of *rss.Feed")
}
f, err:=ct.defaultTranslator.Translate(rss)
iferr!=nil {
returnnil, err
}
ifrss.ITunesExt!=nil&&rss.ITunesExt.Author!="" {
f.Author=rss.ITunesExt.Author
} else {
f.Author=rss.ManagingEditor
}
returnf
}
Next you must configure your gofeed.Parser to utilize the new gofeed. Translator :
Every element which does not belong to the feed's default namespace is considered an extension by gofeed . These are parsed and stored in a tree-like structure located at Feed.Extensions and Item. Extensions . These fields should allow you to access and read any custom extension elements.
In addition to the generic handling of extensions, gofeed also has built in support for parsing certain popular extensions into their own structs for convenience. It currently supports the Dublin Core and Apple iTunes extensions which you can access at Feed. ItunesExt , feed.DublinCoreExt and Item.ITunesExt and Item. DublinCoreExt
Default Mappings
The DefaultRSSTranslator , the DefaultAtomTranslator and the DefaultJSONTranslator map the following rss. Feed , atom.Feed and json.Feed fields to their respective gofeed.Feed fields. They are listed in order of precedence (highest to lowest):
请发表评论