![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@bjornharrtell/pinia-json-api
Advanced tools
pinia-json-api extends Pinia Store with capabilities to fetch typed data models via an JSON:API endpoint into record instances.
pinia-json-api extends Pinia Store with capabilities to fetch typed data models via an JSON:API endpoint into record instances.
A PiniaApiStore is defined with an endpoint and model definitions and the store instance API provides methods findAll
, findRecord
to fetch record(s). PiniaApiStore will automatically resolve included relationships. If relationships for a record are not included they can be fetched later using findRelated
.
Records are shallowReactive and if previously fetched they will be updated by subsequent fetches.
A service returning the canonical example JSON:API document at https://jsonapi.org/ can be consumed by a store defined in this way:
import { definePiniaJsonApiStore, Model, type ModelDefinition, RelationshipType } from 'pinia-json-api'
export class Person extends Model {
firstName?: string
lastName?: string
twitter?: string
}
export class Comment extends Model {
body?: string
}
export class Article extends Model {
title?: string
author: Person | null = null
comments: Comment[] = []
}
const modelDefinitions: ModelDefinition[] = [
{
type: 'person',
ctor: Person,
},
{
type: 'comment',
ctor: Comment,
},
{
type: 'article',
ctor: Article,
rels: {
author: { ctor: Person, type: RelationshipType.BelongsTo },
comments: { ctor: Comment, type: RelationshipType.HasMany },
},
},
]
export const useArticlesStore = definePiniaJsonApiStore('articles', {
endpoint: 'http://localhost/api',
modelDefinitions
})
The above store can then be used as follows:
import { useArticlesStore } from './stores/articles'
const { findAll } = useArticlesStore()
const { records: articles } = await findAll(Article, { include: ['comments', 'author'] })
expect(articles.length).toBe(1)
const article = articles[0]
expect(article.id).toBe('1')
expect(article.title).toBe('JSON:API paints my bikeshed!')
expect(article.comments.length).toBe(2)
expect(article.comments[0].body).toBe('First!')
expect(article.comments[1].body).toBe('I like XML better')
expect(article.author?.firstName).toBe('Dan')
FAQs
pinia-json-api extends Pinia Store with capabilities to fetch typed data models via an JSON:API endpoint into record instances.
We found that @bjornharrtell/pinia-json-api demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.