Add graphql types to the Seo module
This PR fixes #11199
Added ObjectGraphTypes for SeoMetaPart and needed to add one for MetaEntry, too. I'm not sure if OrchardCore.Seo is the right place for the ObjectGraphType for MetaEntry though, so I would like some feedback on that.
Rest is working fine:

@sebastienros Dont who to ping to look at this but I think it's somewhat in a reviewable state now
@dannyd89 is your PR ready or still WIP?
@hishamco I removed the WIP label, this is ready for PR
Also I'm not sure how to make the SeoMetaPart fields queriable since I'm getting an exception in GraphiQL currently. Do I need to add an IndexAliasProvider in the same fashion as for example AutoroutePart has one?
I'm not sure about that one, need to ask @carlwoodhouse but that would definitely make sense.
Also I'm not sure how to make the SeoMetaPart fields queriable since I'm getting an exception in GraphiQL currently. Do I need to add an IndexAliasProvider in the same fashion as for example AutoroutePart has one?
I'm not sure about that one, need to ask @carlwoodhouse but that would definitely make sense.
This one is already fixed with the current commit, I'll work on your feedback as soon as I have some time on my hand, thanks
@sebastienros I addressed your feedback and removed all the indexing etc
I recreated the internal SEO module with my code as an own module and we are currently using it successfully. Is there still something I can do to close this? Else we will stick with our own module.
Waiting on release 1.4 before anything.
Waiting on release 1.4 before anything.
Thanks for the reply, I'll wait and continue to use my module then for the time being
Hi is there any progress on this issue? I would be very nice to have these fields in graphql? Maybe I can help to resolve the merge conflicts if you like to.
I was still waiting on approvement for this, I would be happy if this PR could resolved/merged at some point
I was still waiting on approvement for this, I would be happy if this PR could resolved/merged at some point
Done!!
GeoPointField also have same problems
Please resolve the conflict
Closed?!!
Sorry for the confusion, should be good now