Hacker Newsnew | past | comments | ask | show | jobs | submit | PondSwimmer's commentslogin

https://github.com/PacktPublishing/GraphQL-Best-Practices

And here are free examples from the book


No. We produce a lot of open source - we can definitely provide version to self-host later.


> We produce a lot of open source

Got a link?



Good idea! We will add it!


I'd love this service but how are you going to handle bots? I wanted this for my personal website which will maybe receive an email once per month in the best case scenario, but with lambdas there is always the risk of having a malicious actor coming in and pushing your bill to astronomical levels


Yes but mailik only sends mails to your addresses not clients. However we will think how to filter spam ofc


Oh then I misunderstood.

Sending to in-the-loop third parties is a must. I’ve set up 1 form that goes to me directly and hundreds which go to others.


Maybe just sending the confirmation without the actual message. World is transforming and sending to people who filled out the form may open the gates to spammers. What do you think?


I think looking at how Gravity Forms (and similar) handles this within the WP ecosystem is a helpful starting point. A lot of expectations around what a form service does and doesn't do are set by those plugins – for better or worse.

I personally believe that sending a confirmation to the person filling out the form is a requirement, in some cases, and not having it would be a mistake.

Forms are tough! Glad ya'll are working on it.


Ok I will definitely take a look. Making integrations is a good next step for mailik. Thank you very much!!!


Curious to hear if you generally prefer to manage client's forms and billing through your own account or have them create their own and share credentials with you?


I think in a full build out, being able to manage forms+billing through a "developer account" that allows me to manage their stuff would be nice.

I would _especially_ like that the developer account gets like 3 free forms as long as clients are paying.


This idea needs exploring. It is good, but a little bit complicated.


I think there are 2 situations: - 1 client is not technical at all - so you manage on your acc - client is ok with having their own acc, then it is much better option


That makes sense. Are you currently using something more involved, e.g. Form Spree?


nope


Thanks for that! It will help us create a direction for mailik. Obviously we are small team that does side-projects from time to time, but we can take what's useful from it.


Hi,I made a small framework that you can use with graphql-yoga or apollo-server. It is a type-safe wrapper for backend like GraphQL Zeus is a type-safe gen for frontend, but there is more.

I added also:

micro-federation - have multiple schemas and resolver files in one repo while axolotl merges them using open federation spec. It can also join resolver groups.

inspect command - inspect your resolvers in terminal to see which fields are implemented and which not

modularium - with just 2 modules now. A concept for schemas that are brought together with resolvers to attach to your backend and schema - for now users and teams modules.

custom scalars support

simplified directives support

Docs: https://axolotl-docs.vercel.app/ I started this framework after my talk on Programistok in December and I will maintain it. Tell me if you have any other ideas what I can add that can help small & medium projects to be started faster.

Artur


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: