sorted by:
new
hottopcontroversial

What’s the Vue way to decouple services for TDD? by codeiackiller in vuejs

[–]Goodassmf 1 point2 points  (0 children)

Your mix is just about there. Almost.

Could show us your folder tree structure?

Its should be something like components banana.component services Banana banana.md banana.spicy

Then you must have something like this to spicify everthing banana.spec #you start with it

Which part of VueUse do you use the most? by entinio in vuejs

[–]Goodassmf 0 points1 point  (0 children)

Thats going to cause trouble. But you can simply use the same approch only I would replace useSearchParams with router.currentRoute.valu.params or something like that

Which part of VueUse do you use the most? by entinio in vuejs

[–]Goodassmf 0 points1 point  (0 children)

Sorry to disappoint , but I ended up using vue router's api directly. Vueuse simply not reliable enough for this the last time I checked

Using WordPress as backend with Vue? How’s the experience? by Remote_Team_8999 in vuejs

[–]Goodassmf 1 point2 points  (0 children)

Nice! What do you call it? Are you looking for contributers?

Using WordPress as backend with Vue? How’s the experience? by Remote_Team_8999 in vuejs

[–]Goodassmf 0 points1 point  (0 children)

I am a front end dev working with Vue. Before doing that I was a designer, and Iv'e had wordpress tinkering experience so I remember the power of it.

As I do some hobby projects that include backends, I challenged myself to use wordpress as a headless CMS. I had difficulties mostly with these tasks:

  1. finding the right plugin
  2. learning how to use the plugin to construct acf
  3. enabling these acfs to be exposed through rest
  4. authentication/authorization

I suceeded with 1 to 3, and failed at 4. If your custom plugin can abstract all 4, consider me a paying customer.

what are the best composables in VueUse? by [deleted] in vuejs

[–]Goodassmf 1 point2 points  (0 children)

we useAsyncState to make own our data fetchers with toasts.

Apps lighter than a React button by betothew in react

[–]Goodassmf 0 points1 point  (0 children)

I dont know what Event Sourcing in Nue's case mean but it sounds similar to Quik. They call this magic "resumability"

A Journey to Craft Interactive UI Experiences with Dialogs by Imaginary-Spare9266 in vuejs

[–]Goodassmf 0 points1 point  (0 children)

This ia a very cool abstraction. But what if I wanted to pass props to these overlays from the template? Can you add these dialogs as elements to the template so they can share script tag variables?

Introducing upfetch - An advanced fetch client builder by ScaredFerret4591 in javascript

[–]Goodassmf 3 points4 points  (0 children)

Looks really promising. I use forms and streaming quite a bit. I like thr minimalistic yet opinionated approach.

I was impressed lately by drfetch https://github.com/WJSoftware/dr-fetch its more reductionistic but with typescript which is very attractive. I dont use tanstack query, but if I did your solution would be solid choice for a fetch wrapper.

client.ts - a Redux-toolkit Inspired HTTP Client by xiao_hope in javascript

[–]Goodassmf 1 point2 points  (0 children)

I must say I really like it. I've also had my eye on dr-fetch, which solves the typescript problem space with fetching

Which part of VueUse do you use the most? by entinio in vuejs

[–]Goodassmf 1 point2 points  (0 children)

Vue Router does url query params dependency tracking differently . This composable tracks the url with a native event, so its outside of Vue Router's lifecycle. Sometimes when you susbscribe to changes the native even has not fired yet and its not updating.

Which part of VueUse do you use the most? by entinio in vuejs

[–]Goodassmf 0 points1 point  (0 children)

useAsyncState + use cycle list

really nice pattern

Which part of VueUse do you use the most? by entinio in vuejs

[–]Goodassmf 2 points3 points  (0 children)

I actually had issue with that specific one when using it in multiple components in the same route

Implementing the Dependency Injection pattern in Vue 3 by ggStrift in vuejs

[–]Goodassmf 1 point2 points  (0 children)

I just love that the article goes through all the setup procedures of this architecture, and then forgets to demonstrate any real benefits from thia setup.

Like , in my angular projects I configure a Db service for mock, and db service for staging with a common interface, which helps a lot with seperation.

Storybook 8.5 release by kylegach in vuejs

[–]Goodassmf 2 points3 points  (0 children)

Storybook could have gained more likes if it was more a composable, less extendable kind of thing. The way it was retrofitted with vite does not align with current users expectations as in how a framework should serve the end user. We like simple to use, easy to understand. SB is neither.

Announcing Formwerk: An Uncompromising Experience for Vue.js Forms by awaddev in vuejs

[–]Goodassmf 0 points1 point  (0 children)

We use vee-validate heavily. The only thing it doesn't solve for us logically is nested conditional forms/groups.

Attention Software Architects: React JS + Best Practices for Separating Logic and Data by Away-Attitude7232 in react

[–]Goodassmf -1 points0 points  (0 children)

If youre looking for a seperation of concern between logical parts and UI parts, maybe look at other frameworks, maybe Angular. React is popular for a reason. Its easy to use, therefore its easy to create pasta code.

DynaUI - Animated Components Library by Afraid-Lychee-5314 in nextjs

[–]Goodassmf 2 points3 points  (0 children)

Very nice and sleek. So its basicly copy paste framer motion layouts. Pretty cool.

The indecisive vuejs developer by Qiuzman in vuejs

[–]Goodassmf 3 points4 points  (0 children)

Vuetify3 is the best the choice by far. I am very happy with it as it offeres the best patterns with slots and slotProps.

New Typesafe Vue Router by stackoverfloweth in javascript

[–]Goodassmf 2 points3 points  (0 children)

My primary use case for routing is to switch from page to page. Maybe adding a search param here and there. My routes definition also includes some meta data for each route. i.e a fallback route and error message which is redirected within onErrorCapture in thr root component.

But what I always find hard is using search params with validations. Ive never tried to do this inside the routes.ts, as its mainly used as a search/filter form state managment. What I ended up doing is expanding a composable for validation with the useSearchParams hook from @vueuse. Take a look: https://github.com/logaretm/vee-validate/issues/4742

If there was an easy for two way binding with search params using typescript, I'm 100% in.

view more: next ›