Atom Support

[ddkasa]

Made the changes as discussed in #46.

I made some directory changes to accommodate the new Atom model. Otherwise kept to the same code style as used for the RSS model. Works when testing with the sample Atom XML provided, but can't seem to get the tests working as the JSON dump formatting is giving me problems.

Let me know what you need to change before merging or how to approach the testing.

[dhvcc]

I'll go over standarts for Atom a bit later, here's a couple of comments regarding the structure

[dhvcc]

Nice PR, as I said, I'll go over spec for Atom a bit later, however, thanks for contributing, if any of the parts from my comments are unclear or you don't have time to implement them - ping me, I'll help answering or coding

[dhvcc]

Also, this should fix tests

--- a/tests/samples/atom.json
+++ b/tests/samples/atom.json
@@ -63,7 +63,7 @@
             },
             "published": {
               "attributes": {},
-              "content": "2003-12-13 08:29:29-04:00"
+              "content": "2003-12-13T08:29:29-04:00"
             },
             "rights": null,
             "source": null,
@@ -126,7 +126,7 @@
       },
       "updated": {
         "attributes": {},
-        "content": "2005-07-31 12:29:29+00:00"
+        "content": "2005-07-31T12:29:29Z"
       }
     }
   },

[ddkasa]

Alright, tests are working now as well. Let me know what I need to change for the Atom spec as well.

[dhvcc]

Hey, know this is a lot of comments, but it's just due to us not having a clear plan of development before implementation. I'll try to raise a PR for your branch in your repo so we can merge it faster

[dhvcc]

@ddkasa Whoops, accidentally commited straight to your branch, I apologize, wanted to create a branch to show you the diff with the fixes. Please check out the diff and let me know what you think

[dhvcc]

LMK if this seems good to you and I'll merge

[ddkasa]

Looks good to me.

Initially had a bunch of sub-models setup, but decided to remove before submitting to keep it more simple.

Regarding removing the root_key. There might be some deprecation issues with that and also in terms of syntax further down the line would be awkward as you would have to use parsed_model.rss.foo... before accessing the feed every time.

[dhvcc]

@ddkasa there is a way to backport even when removing, but I agree on using model.rss.blah.blah
I'll think about it, but I think it's ok. I'll prepare a release after the decision, let me know if this is urgent for you/your project