Added notification item code

[Megha-Dev-19]

Resolves #505

[Megha-Dev-19]

@elliotBraem @ailisp
After getting this merged I will ask Eugene to update this to devhub.near account
and I have created a draft PR for near org here
please let me know if any other change is required or if I m wrong somewhere
And if there is any way to test these changes
Thanks

[elliotBraem]

Then this <a tag should have

href={to={href({
    widgetSrc: "${REPL_DEVHUB}/widget/app",
    params: {
      page: "post",
      id: props.id
    },
  })}

Although according to the story, the issue here is that for blogs, we should be pointing to blog instead:

to={href({
    widgetSrc: "${REPL_DEVHUB}/widget/app",
    params: {
      page: "blog",
    },
  })}

But we don't have access to the post type at this moment...

Maybe when we create the notification (author posting the blog), we could pass the postType of where it's coming from?

[ailisp]

The other way could be redirect on the post widget, if it's a blog type, redirect to related blog page

[Megha-Dev-19]

yeah we don't know when it's a blog or post notification

[elliotBraem]

@Megha-Dev-19 it's a good start!

As per testing, this is something we could do:

For near.social, copy and paste the mob.near/widget/NotificationFeed code to local (and any relevant child components) so that we are serving the code locally. It could just be to a temp directory under src/ or something like that.

Then, we can create or edit a blog from devhub-test community, adding a mention to your name. We should be able to look at this new notification through our local "forked" notification feed.

[Megha-Dev-19]

@elliotBraem @ailisp can we merge this PR.? Will update the code further according to contract changes?
I have applied your suggestions

[ailisp]

This looks good to me. @elliotBraem Could you review again? It's currently blocking from your request changes.