woutercouvaras

I'm sure there must be someone else out there that gets a bit frustated with examples that only ever show simple cases of working with complex data/forms. I'm talking specifically about large blocks of data that are deeply nested...

I thought I'd put together an example that shows *a* way that one could do something like this. This is quite simple and really just shows how one can split the forms up and then validate and sanitize all of it from the parent. It shouldn't be too hard to expand on the setup.

I'm sure there must be someone else out there that gets a bit frustated with examples that only ever show simple cases of working with complex data/forms. I'm talking specifically about large blocks of data that are deeply nested...

When dealing with large bodies of complex data, one might want to create a series of components for each "section" of data and have that component be responsible for the display, validation, custom data transforms, async lookups, etc.

I’m not a big one for New Year stuff, but given that there’s a natural break at the end of the year (esp in the Southern hemisphere, given that it’s out summer), one almost can’t help but stop to think about the year ahead. I’m still trying to figure out what I want from this year…

One of the downsides to living in the southern hemisphere is that, unlike the northern hemipshere, Dec really is the end of the year. Think; school plays, graduations, end of year work functions, Christmas parties, etc, etc...

It only really dawned on me when chatting to an American friend (now living in Cape Town) who, when I reflected our good weather and longer holidays leading up to Christmas etc, said that the upside of nothern hemisphere is that life is generally "quieter" around Christmas.

One of the downsides to living in the southern hemisphere is that, unlike the northern hemipshere, Dec really is the end of the year. Think; school plays, graduations, end of year work functions, Christmas parties, etc, etc...

In PixelPaper and in my contact work, I've been working with some big (and deeply nested forms). I use Vuelidate to handle my validations and wow, it's really powerful! When I was just learning vue, I bought Adam Wathan's Advanced Component design course...

And that's that folks. No more prop drilling or stacks of event emitting to do. Of course if you use somethingn like NuxtUI (which is amazing), things might looks a bit different because of hte way their form component works, but it's a pretty easy solve...

In PixelPaper and in my contact work, I've been working with some big (and deeply nested forms). I use Vuelidate to handle my validations and wow, it's really powerful! When I was just learning vue, I bought Adam Wathan's Advanced Component design course...

E.g. in your parent you might have a reactive obj called "myForm": <Child v-model:my-form="myForm" /> Now, any state changes in the parent or the child are in sync. Not enough magic? I've got you! Instantiate Vuelidate in the parent and in the child...

In PixelPaper and in my contact work, I've been working with some big (and deeply nested forms). I use Vuelidate to handle my validations and wow, it's really powerful! When I was just learning vue, I bought Adam Wathan's Advanced Component design course...

I've been sick for two weeks, and then simply just too tired to work after hours, so progresss has been near non-existent. There's so much going on here that I'd have to write and essay to explain it all, but in short, each of these components has always been able to handle their own validation...

About 18 months ago, I stopped actively running my agency to focus on building my own product, PixelPaper. I didn't have the capital to do this without working though (I have 5 kids and my wife home schools them, so if I don't work, we don't eat)...

For anyone interested, PixelPaper is a "website builder" of sorts. I've built it to solve some of the problems I faced while building sites for customers, so I'm hoping it will help others (customers and developers) in this space too.

About 18 months ago, I stopped actively running my agency to focus on building my own product, PixelPaper. I didn't have the capital to do this without working though (I have 5 kids and my wife home schools them, so if I don't work, we don't eat)...

So my current plan is to get v1 of PP out, port some of my existing customers onto it and then start building some more sites after hours, all powered by PP.

About 18 months ago, I stopped actively running my agency to focus on building my own product, PixelPaper. I didn't have the capital to do this without working though (I have 5 kids and my wife home schools them, so if I don't work, we don't eat)...

Part of the reason for this is that I'm just not earning enough. Rule #1 as an entrepreneur is to ensure you stay in the game, so I need to start earning more to get PixelPaper off the ground.

About 18 months ago, I stopped actively running my agency to focus on building my own product, PixelPaper. I didn't have the capital to do this without working though (I have 5 kids and my wife home schools them, so if I don't work, we don't eat)...

so I negotiated a deal with a client and former business partner to sell all my time to them. The idea being that I'd have less noise (running an agency can be pretty noisy) and thus have more time to spend on my product.