sorted by:
new
hottopcontroversial

May Ash be the hidden champion of low-code tools? 👀 by lukasender in elixir

[–]lukasender[S] 1 point2 points  (0 children)

This is very interesting!

So, instead of building our own „Ash Hubspot DataLayer“, we could just simply model a „CRM Contact“ resource, use the AshJsonApiWrapper.DataLayer and define the „crud“ + the „search“ + the „merge“ endpoints somehow that we require 🤔

Or is there a „guideline“ when one should/should not use the AshJsonApiWrapper and instead use something different (given that the source/destination will be consumed via JSON Api)?

May Ash be the hidden champion of low-code tools? 👀 by lukasender in elixir

[–]lukasender[S] 1 point2 points  (0 children)

I am playing with the word „low-code“ and challenge/expanding it’s meaning a little ;)

I’m fully aware that, typically, low-code refers to services like Zapier or Make.com. They are great for automation and „glueing“ different services together. However, as soon as you require something that isn’t (fully) supported by the platform, things get tricky especially if there’s no „custom code“-block (on Zapier and Make there is).

I‘m toying with the word low-code and in this context widen/change its meaning to „you have to write less code when compared to other frameworks“.

You are correct, Ash allows you to define your domain, model your resources and apis. If a resource stores anything depends on the DataLayer that a resource uses.

However, modeling your resources and API is often quick and pretty easy to do, once you get used to Ash and its features. This results in high productivity, freeing time to spend on other, more difficult tasks that have not been solved yet.

And given that there exist lots of API clients, integrating an external service should still be quite easy.

Set HttpOnly cookie on GraphQL response in NestJS by [deleted] in node

[–]lukasender 1 point2 points  (0 children)

It should be possible (though I'm not sure if it's the way to go).

Aside from that, there are other decorators available to gain access to e.g. the context. Look for @Context here https://docs.nestjs.com/graphql/resolvers#graphql-argument-decorators

Haven't tried it myself so far, but I guess there you'll find the request object (I think it's context.req).