found 10 vulnerabilities (5 low, 5 moderate) in 6529 scanned packages
10 vulnerabilities require manual review. See the full report for details.
Hi @dyspop, just learning KS (and Javascript!) as well, I think the SydJS website is a great place to start to learn more advanced features, as it's available on GitHub. You find it along with other examples (not opensource though) on the KS examples page: https://v3.keystonejs.com/examples
`var q = keystone
.list('Service')
.paginate({
page: req.query.page || 1,
perPage: 2,
maxPages: 5,
})
.where('state', 'published')
.sort('-publishedDate')
.populate('author cateservice');
if (locals.data.categories !== null && locals.data.categories._id) {
q.where('cateservice').in([locals.data.categories._id]);
}`
Can you please explain your usage of @hari-zeptoh
App is for the mobile or web app.
I was thinking in accessing it using something like the session, but I'm really new to the KeystoneJS API and actually was looking into the official docs, but couldn't find anything related... best shot next was going on ExpressJs doc maybe?
What I'm trying to do is that whenever a user sends a message it takes the user (hence why I'm trying to send the current user) and assigns it into a collection as the author of the message (
author is a relationship inside Messages model, which should be, of course, the author of the message, or who sent it.)
Hi @hari-zeptoh you need to use https://github.com/keystonejs/keystone-storage-adapter-s3 package for upload image on S3
how can i update my currect version of the keystone am in beta version i need to switch to stable one?
my current version is 4.0.0-beta.5
Is there any way to show a related "subfield" for Relationship field? Not just the mapped "name". Say you had invoices with relations to payments, could you show a field from "payments" related records in the main invoices list view, in the admin UI? The only way I can figure to do it is create a field that gets updated when the record saves, but this seems very inneficient.
Not sure if the maintainers are here, but this pull request addresses a blocking bug of core functionality for Keysonte 4.x, it makes it that anybody that uses a Boolean field can't upgrade past RC1 of 4.x without bad things happening. Could this please get pulled in? I really want to get to Node 8 and the latest releases, but just can't until this gets merged. I know the focus is on 5, but this has been broken for a long while. Sorry to make my case here, but it needs attention. keystonejs/keystone#4927
Hi guys, who ever has a blog or post on Medium stuff that are related to programming, I am working on a new publishing platform, its my side project and i worked reallllly hard on it - I would love for your feedback! if you love publishing and curating content - PLEASE PM ME :)
if my message is not following chat room rules i will delete it! thanks.
if my message is not following chat room rules i will delete it! thanks.
There are lot of supported commands and some others are not. https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html
Anyone has used this with keystonejs?