MattV
Khoros Staff
Joined 18 years ago
User Profile
User Widgets
Contributions
Re: HTML support for GraphQL API
If I had to guess, I would say you could. I think even in community classic we were able to manually put in those <li-asdf> tags into the message body, and as long as it resolved to an actual object and ID, it would work. Aurora uses GraphQL for 100% of its interactions with the DB/Backend, and I'm quite certain we save those tags to the DB. So, what you can do for any Aurora operation, is "do the thing" with brower dev tools network tab open. You may need to make sure to "preserve log" in case the page reloads. You will see a "graphql?opname=Something" in the requests. If you look at the payload of that request, you can see the data they are sending to graphql. The "opname" you see in the network requests just map to a .query.graphql (or .mutation.graphql) on the backend, with relevant variables set. So only sort of gotcha with this is it may not be immediately obvious which graphql query or mutations they are using,904ViewsSign in to react to this post0CommentsRe: Handlebars custom component not executing GraphQL query
Try this {{#gql "privateUserStats" variables=(hash id=(join "user:" user.id ""))}}ViewsSign in to react to this postComment- ViewsSign in to react to this postComment
Re: editable content in react or handlebars component
There is not any good OOB way to do that. I had experimented with creating a Handlebars editor in React, and it is a bit complicated depending on how fancy you want to get. I used the @monaco-editor/react package for the editor (monaco being the underlying editor used for VS Code). However, this isn't currently supported by the SDK (not an approved dependency), so this wouldn't work in production code for now. Then there's a couple GraphQL queries/mutations you can use to get and save the components. query GetComponents { components(markupLanguages: [HANDLEBARS], grouping: [CUSTOM]){ id template{ id style content defaults { config { applicablePages description } props { id } } components{ id } } } } mutation SaveComponent($id: String!, $componentId: String!, $content: String!, $applicablePages: [ComponentPageScope!]!, $description: String!) { createOrUpdateComponentTemplate(templateInput:{ id: $id markupLanguage: HANDLEBARS content: $content defaults: { config:{ applicablePages: $applicablePages description: $description } props:[] } components:{ id: $componentId } grouping: CUSTOM }) { result { id content } errors { __typename ... on NoComponentsError { message fields } ... on InvalidComponentTemplateIdError { message fields } ... on NoDefaultComponentError { message fields } ... on ComponentTemplateContentCannotBeSavedError { message fields } ... on CreateOrUpdateComponentTemplateFailedError { message fields templateId } ... on ValidationError { message fields key } ... on Error { fields message } ... on ErrorWithArgs { fields message } } } }ViewSign in to react to this postCommentsRe: editable content in react or handlebars component
You can add properties to a component to allow simple configuration. For example, the following component json: { "id" : "Announcement", "markupLanguage" : "HANDLEBARS", "defaults" : { "config" : { "applicablePages" : [ ], "description" : "", "fetchedContent" : null }, "props" : [ { "id" : "announcement_text", "dataType" : "STRING", "list" : false, "label" : "Announcement Text", "description" : "Announcement text to display", "control" : "INPUT" } ] }, "components" : [ { "id" : "custom.widget.Announcement" } ], "grouping" : "CUSTOM", "scriptGroups" : null, "aboutThis" : null } Adds a simple input box to the component settings in designer where an Admin can add announcement text. I handlebars, I access the text with {{component.props.announcement_text}}ViewsSign in to react to this postComments- ViewsSign in to react to this postComments
Re: QraphQL Missing constraint on the messages collection
In classic/LiQL the post time constraint ended up being very inefficient, and even inaccurate with larger date ranges. So, assuming this omission is intentional in GraphQL, I'd say it was likely omitted because of similar reasons. I don't know the actual reason though; I'd have to confer with our internal dev teams to confirm the actual reason for post time not being a constraint.ViewsSign in to react to this postComments- ViewsSign in to react to this postComment
- ViewsSign in to react to this postComments
904Views
0Comments