If you're still looking to get some GraphQL working with Umbraco I've started making a package making GraphQL easy with Umbraco. It's far from done but it could give you an idea of how to implement a GraphQL solution 😉 https://github.com/nikcio/Nikcio.UHeadless

We've been testing this out lately at work and it seems highly promising, nice work! Do you have any thoughts on future development of it? Will you be adding Media support eventually? We are still rookies in the context so we're not sure Media means to fetch Media items from the Media library in general, or if it means to be able to extract the images from the content that the web editor has selected. But we're playing around with it, slowly grasping things 🙂

@TackleMcClean 🏅 I'm trying to do on going development on it so more features are to come. Right now I'm trying to get authentication to work with the system. About your media question then you can already get the selected media on the content nodes. Using the url of the media file

Very cool! Thanks for what you've done so far. I saw this tutorial some time ago: And one key takeaway from that for me was how the underlying database query is limited to whatever the graphql question is asking for. In other words - queries are smart/efficient. When I was thinking about doing the same thing for Umbraco I realized Umbraco isn't using Entity framework, but Unpoco or something similar. This made me think that maybe it's not that easy to solve in Umbraco. So I wonder, did you solve it in your extension, or is it more along the lines of "ask for all data and then filter out only what's requested"? If you did solve it, was it hard? 🙂

@TackleMcClean 🏅 my package actually works through Umbracos built-in caching layer and doesn't communicate directly with the database. Therefore we need to gather all the data that the cache gives us initially but this isn't that bad because the cache layer is pretty performant. Then there's a bunch of properties for example the absolute url of a node that need to be computed if you what to use it. These elements are therefore only loaded if it is part of your query I've also been building another GraphQL interface at work actually using EF Core and this works great and can be a great way to create effective queries.

Nice! I would definitely have missed that approach, so glad someone knowledgeble solved it. Do you know if images fetched via Content graphql includes focal point position?

You can include it yourself. All properties can be overridden to include everything you'd like. Here I've created what information I'd like from a user picker for example: https://github.com/nikcio/UBlog/blob/main/src/UBlog/Models/CustomPropertyMappings/UbUserPicker.cs And then added it to the configuration in startup: https://github.com/nikcio/UBlog/blob/main/src/UBlog/Startup.cs#L58 You can do the same for something like the media picker to include the focal point. To do this it would properly make the most sense to inherit from this class: https://github.com/nikcio/Nikcio.UHeadless/blob/main/src/Nikcio.UHeadless/UmbracoContent/Properties/EditorsValues/MediaPicker/Models/MediaPickerGraphType.cs Then you don't have to worry about the setup for the already existing data that by default is generated for a media picker

Awesome info, thank you! We are currently trying to implement something like this. Do you know if it is possible to supply type hinting for the visual graphql bananahotcake thingie? So the interface there knows whats up?

@TackleMcClean 🏅 The visual GraphQL interface does already have type hinting for everything but the properties on a content node. The properties can be so different from one another that i couldn't find a way to create type support for the property values. Might come in the future if I figure something out. And yes the grid editor is not supported by default. I don't really use it anymore because I think the Block editor gives a more user friendly model. So I didn't have a good starting point for structuring the data for a grid editor. The error it gives is because it tries to use Umbracos models that are self referencing which is also the reason we need to make our own models. The typos will be fixed in the next release 😉 I also need to do a good amount of restructuring of the options for everything so it's more developer friendly. But also feel free to create PRs if you find anything that stand out. I only have time to work on the project about once a week so it's being built over short sprints😅

We probably won't need grid editor support any time soon, it was more of a double check if I was seeing things correctly.

The type hinting I'm thinking of is what you can see under "schema reference" in the GUI. Are you thinking of something else? About the page type modification then you can now with version 1.1.0 do this partly because it's possible to use another model for content and property types. Try to look at the extensions here https://github.com/nikcio/Nikcio.UHeadless/blob/main/src/Nikcio.UHeadless/Extentions/UHeadlessExtentions.cs#L47

I think I mean the same thing, but I'm not 100% sure. Primarily the Schema Reference listing, secondarily what you get autocompletion for when typing your query, but I'm guessing the former "drives" the latter. I'll check out Extensions!

Yes that right 😉

God morgon - I put up a PR for the typo fixes I've noticed: https://github.com/nikcio/Nikcio.UHeadless/pull/27

@User Try to check this out. I quick threw a little documentation together on the topic: https://github.com/nikcio/Nikcio.UHeadless/blob/main/docs/contentModels/editContentModels.md

well I have experience with PHP, javascript, and some very ancient actionscript 3.0 knowledge, so I know some basic OOP at least also the general "trying random stuff until other stuff happens" developer approach 😄

I don't know why I can't spell extensions. But yes only two files and some extra code in startup.cs

I've tried following the documentation but I'm running into a couple of errors. First off, just trying to get a custom string, setting up a query that works fine usually:

{
  contentById(id: 1061) {
    myCustomString
  }
}

Results in:

{
  "errors": [
    {
      "message": "Unexpected Execution Error",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "contentById"
      ]
    }
  ],
  "data": {
    "contentById": null
  }
}

Regardless of what property I'm asking for it breaks like this. I then did a guess and tried to do:

{ (builder) =>
                    builder
                        .AddTypeExtension<ContentQuery>()
                        .AddTypeExtension<CustomContentQuery>()
                        .AddTypeExtension<PropertyQuery>()
                        .AddTypeExtension<MediaQuery>()
                };

But it seems you can't include ContentQuery as long as you're including a CustomContentQuery. It fails to compile complaining about middleware order. I also tried extending

ElementGraphType

instead of

ContentQuery

, figuring there was some collision of trying to use something already defined, but same issue. Any guess on what to try?

@User You shouldn't include .AddTypeExtension()

that's what I first did, which led me to the unexpected exectution error it was first after that, that I tried also adding the "old" ContentQuery

What version are you on?

I had no errors whatsever which was confusing me I think I was on 1.3.0, but maybe that's the issue. I changed version to 1.3.0 in my project.csproj file, and then ran

dotnet restore

, however I might be wrong in my assumption that that will give me the latest version? should I also run

dotnet clean

/ remove folders?

It's because automapper cannot map... I forgot to include that in the docs. You need to add the following:

public class CustomProfile : Profile
    {
        public CustomProfile()
        {

            CreateMap<IPublishedContent, CustomContentGraphType<PropertyGraphType>>()
                .IgnoreAllPropertiesWithAnInaccessibleSetter()
                .ForMember(dest => dest.Content, opt => opt.MapFrom(src => src));
        }
    }

I have little clue what that code is doing but it's working now!

It's somthing that tells a package how to convert from one object type to another

Given this approach, is it possible to do more than one custom content graph type? I'm confused by the need to remove the "original" ContentQuery

The original is just a default implementation of the default queries: https://github.com/nikcio/Nikcio.UHeadless/blob/v1/contrib/src/Nikcio.UHeadless/UmbracoContent/Content/Queries/ContentQuery.cs About your need to have one type per document then it's not really possible in that sense because GraphQL would have no way of knowing what type it would return. And therefore nor be able to define a schema. There's a workaround but it requires you to always include properties and have no type hinting for the properties. The idea with chaning the content type should be to include custom properties like for example meta tags. This can then be different for every document type but this is based on your own custom code that populates the property.

hmm ok it's also possible I'm thinking too much in non-graphql terms due to lack of graphql experience my approach might be wrong from the start basically what we're trying to do is to something along the lines of using the "on" statement:

fragment comparisonFields on Character {
  name
  friendsConnection(first: $first) {
    totalCount
    edges {
      node {
        name
      }
    }
  }
}

(example from graphql.org)

I haven't used fragment or the on statement yet so I'm not quite sure how this would work

I was talking to my colleague a bit about this, he mentioned that a common use case is using "unions"