npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

wucdbm-vue-errors

v1.0.0

Published

A Vue.js bindings library for wucdbm/filter-bundle PHP toolbox

Downloads

3

Readme

TL;DR

A Vue.js lib to aid dealing with responses generated by https://packagist.org/packages/wucdbm/filter-bundle

Generally speaking, if you pass an adequate list of Error to createErrorCollection, you can use it with whatever backend you have

It is your own duty to re-assign the error collection to the ref that's holding it in place whenever you receive a new response

Implement your own composables if using GraphQL where your state and errors each sit in a ref() and adapt your error paths

<template>
    <div>
        <input
            type="text"
            v-model="model.description"
        />
        <!--        In your own components, add an "error" prop to the inputs-->
        <!--        And bind it like <MyInput :error="errors.last('fieldName')" />-->
        <p v-if="errors.has('description')">
            {{ errors.last('description') }}
        </p>
    </div>
</template>
<script lang="ts" setup>
import { ref, Ref } from 'vue'
import { createErrorCollection, isBackendError } from 'wucdbm-vue-errors'
import { AxiosResponse } from 'axios'

type MyObj = {
    id: number
    amount: number
    description: string
}

const model: Ref<MyObj> = ref({
    id: 1,
    amount: 0,
    description: 'desc',
})

const api = {
    someApiCall(
        id: number,
        payload: {
            amount: number
            description: string
        },
    ): Promise<AxiosResponse<string>> {
        // whatever
        console.log(id, payload)

        return new Promise((resolve) => resolve('whatever'))
    },
}

const saving: Ref<boolean> = ref(false)
const errors = ref(createErrorCollection([]))

const save = (obj: MyObj) => {
    saving.value = true

    // reset errors before sending
    errors.value = createErrorCollection([])

    api.someApiCall(obj.id, {
        amount: obj.amount,
        description: obj.description,
    })
        .then((response) => {
            // do something - success
        })
        .catch((e) => {
            if (isBackendError(e)) {
                errors.value = createErrorCollection(e.response.data.errors)
                return
            }

            // whatever happened - handle on your own
            alert(e)
        })
        .finally(() => {
            saving.value = false
        })
}
</script>

Enjoy.