joshuaalpuerto / node-ddd-boilerplate Goto Github PK
View Code? Open in Web Editor NEWNode DDD Boilerplate
Home Page: https://joshuaalpuerto.github.io/node-ddd-boilerplate/#/
License: Other
Node DDD Boilerplate
Home Page: https://joshuaalpuerto.github.io/node-ddd-boilerplate/#/
License: Other
Hello, I see that you created this project based on my Node API boilerplate, which is release under MIT license https://github.com/talyssonoc/node-api-boilerplate/blob/master/package.json#L27. Do you mind adding the copyright for my work at the LICENSE file? Thanks.
master
branch failed. π¨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. Iβm sure you can resolve this πͺ.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those donβt help, or if this issue is reporting something you think isnβt right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project β¨
Your semantic-release bot π¦π
Here
src\interfaces\http\modules\user\instance.js
We have this code:
const container = require('src/container') // we have to get the DI
const { get, post, put, remove } = require('src/app/user')
module.exports = () => {
const { repository: { userRepository}} = container.cradle
const postUseCase = post({ userRepository, ??? })
Question, if in my case to store User there is need to update several repositiries, I should add it here, but why? Is this responsibility of external Interface to know what repositories are needed to store entity?
Please pardon my ignorance but what's the best way in this to whitelist the routes which do not need authentication like say /register
Add semantic-release
setup and badge
What's the swagger-ui's URL ? I can only access the json at http://localhost:4000/api/0.1/swagger.json
for example.
Thank you
First of all, thank you very much for this boilerplate. Helped me a lot.
My problem is that after registering a user, when trying to get a token with the credentials bcrypt.compareSync(password, encodedPassword)
always returns false.
Am I missing something? I have tried it with a lot of different users but nothing works for now.
const comparePassword = (password, encodedPassword) => {
return bcrypt.compareSync(password, encodedPassword)
}
All I can think of is that user.password in postgres might be text and somehow text and string comparison doesn't work as expected?
How would you recommend nested models be queried from app get.js classes?
I am a bit lost. I have changed only the port and version in .env but I am getting the 404 in the same.
And because of that Failed to Load Spec at this: http://localhost:5000/docs and at Explore.
What could be the issue? Or anybody has seen same thing?
Why useCases
are definede insid Interfaces and relying in Application?
Shouldn't they be part of Domain? What am I missing here?
OOTB support for Pub/Sub so as to delegate chained updates/actions. Background tasks to perform certain needed activities.
|-- src
| `-- user
| |-- domain
| |-- app
| |-- routes
| |-- repository
| `-- companies
| |-- controllers
| |-- models
| |-- views
| |-- repository
`-- config
`-- lib
`-- spec
`-- vendor
Advantages
Question.
There is direct import of module from Application layer
const { get, post, put, remove } = require('src/app/user')
inside /interfaces folder
src\interfaces\http\modules\user\instance.js
Is it ok? Feels like a bit dirty, when we have this whole DI thing.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.