Closed kjdelisle closed 5 years ago
Using the existing ParameterObject definitions, and your OpenAPI spec, make a new custom Sequence extension that automatically converts incoming requests into POTOs (Plain Old TypeScript Objects) that will simplify handling of incoming arguments and parameters.
Example:
const offsetSpec: ParameterObject = {
name: 'offsetSpec',
type: 'number',
in: 'query',
};
const pageSizeSpec: ParameterObject = {
name: 'pageSize',
type: 'number',
in: 'query',
};
const List: RequestObject = {
parameters: [
offsetSpec,
pageSizeSpec,
]
};
class MyController {
@operation('get', '/', {responses})
@request(List)
list(list: List) {
// Auto-populate a List (RequestObject) instance based on provided values
}
}
See https://github.com/strongloop/loopback-next/issues/476 for a complete proposal.
ListRequest extends List
) to transform those objects into logical model instances for ease-of-use in your Repository implementation(s).Assuming no technical blockers, I'd roughly estimate this to take approx. two weeks for development and unit testing
I would be willing to build this myself, with some help of course. :)
I just created a wish list for potential extensions to inspire discussions - https://github.com/strongloop/loopback-next/issues/512.
Log changes performed on models. It would help to keep track of who used, created or changed an entity and the point in time this happened.
The same model that is being audited would be created with added properties mentioned in what should be stored section. This model will get updated when audit action happens.
Cross-posting from #119
I'm opening this thread to discuss and define a scope for real-time functionalities possibly provided by LB-Next.
Currently there are implemented functionalities like event streams, but honestly are not helpful at all when building real life applications, therefore I have built several real-time approaches on top of loopback, which I believe 2 were the most important.
1.- Implemented PubSub functionality. 2.- Implemented Firebase alike interface.
Restrict certain model properties to different user types. For example, a user model could have an account-type property that could only be changed by an admin and not by the owner (but the rest of the model could be changed by the owner).
I don't think I'd know where/how to start - but I could definitely try with some guidance.
Loopback mqtt/amqp support.
make an extension for MQTT protocol.
Will You Build It?
i am willing to contribute , and need guidance .
Make a custom API and expose it to explorer https://groups.google.com/forum/#!searchin/loopbackjs/swagger%7Csort:date/loopbackjs/l6FQGCjNpEY/rrTqHFbZAQAJ
Make a custom API and generate swagger def from it. Same as #1 above except make sure the export to swagger works
Improved error handing for APIs using 400 and 500 HTML status codes and allow the explorer to test those cases
Generate swagger properly from #3 above
Ability to defined a API that is NOT attached to a model
Perhaps
Please remove whatever is implemented. I have not read 4.0 docs completely
I would definitely like to contribute if I have guidance
@ganeshkbhat Great list! Is there any one in particular you would be interested in starting with, depending on which we can see who can help with the guidance from the team.
Thanks for those who've posted their wish list / ideas in this issue, I've copied your content to #512, so that we have one place regarding the extension wish list. Please continue the discussion in #512 instead. Thanks!
Closing it in favor of #512.
@strongloop/loopback-next
Overview
We're looking to see what sort of extensions people would like for loopback-next. Building a list of desired functionality that you want to see will give us a list of ideas to work with.
Once we've got a list of extensions, we'll begin reaching out to you to work with you to make these components/extensions. The goal here will be that you, the community, will own these extensions.
We'll work with you to build these items, and as they progress, we'll get feedback on things like:
Post Your Ideas
Make a comment below with your idea, and include the following:
Vote for Ideas
If you like an idea:
If you don't like an idea:
If you're dead-set on making an extension, feel free to start as soon as possible! Not a member of @strongloop/loopback-next ? That's okay! We still want to hear from you!
Feel free to share links to this issue to everyone you think would love to participate!
UPDATE: See below for an example proposal. There's no particular template, so feel free to phrase it in whatever way suits you, as long as you cover those three bullet points.
UPDATE#2: There are more wish list for potential extensions in #512