This is a technical test for the Majelan Node position. It is a simple web app that allows users to manage their audio content.

The app is composed of one domain, the "program creation".

I've written it using the bootstrap function that was provided to me, and I've added a few things to make it work.

• Nestjs as a framework. I could infer from the bootstrap function using Fastify that is probably the direction you wanted me to go in but quite honestly writing a server from scratch is a bit of a pain and I don't think it's a good use of my time, or yours. I figured I might be able to show you something more interesting ; and more entertaining as well.
• Graphql. Honestly, I've been using it for the past 5 years but never got around writing some close to the Relay specification, so this is my shot at it.
• Typeorm. I've been using it for the past 5 years as well, and I'm quite fond of it. Code-first, clean and readable entities, migrations, and a lot of other things that make it a great ORM ; and it's not even that slow.

So what do we have here? And how do I check it?

• A fastify server, with a graphql endpoint.
• yarn start will run the server
• then navigate to http:https://localhost:8080/graphql to access the graphql interface.
• You can check the docs there for the endpoints, plus test my queries as you wish.

Some things I've done that I'm quite proud of:

• A global object ID dealt with at resolve time, meaning any object in the application has a unique ID and can be queried by it via a single endpoint, relay-style!
• Good two-way resolvers, meaning the program can be found from a given media and the other way around.
• A smart way to order medias in a program using self-referencing.

What I didn't take the time to do, because I guessed it wouldn't be that interesting to you:

• a nice domain-error layer. Typeorm and GraphQL both output meaningful errors (most of the time) so that should be enough for now.
• An endpoint to remove medias from a program. I figured it would be the same logic as adding a media to a program, but in reverse. Feels unecessary to show-off but I'd be happy to do it if you want me to.
• Clean DTOs. My output types are sometimes a bit messy in the Graphql resolvers but I'd rather fit the spec than take too much time on something I feel is trivial.
• Super in-depth documentation. I've written a few comments here and there but I didn't take the time to write a full documentation. I'm not sure it's necessary for a technical test, but I'd be happy to tell you everything over a call.
• The migrations utils. I've set the database to synchronize on app-startup so migrations run every time.

Fork this repository to work on it as you would usually do. Once you're done, send us the URL so we can take a look!

This test uses Yarn, along with Docker to get you running quickly with a MySQL Database. You can start the containers and get running with the following commands:

docker compose up -d
yarn start

The api service will run on port 8080, the web service will run on port 3000. Open http:https://localhost:3000 with your browser to access the web app.

Clients want to organise their own content. They have audio files which they want to upload and organise into programs. They also want to be able to edit and delete their content.

You will have to create the endpoints to manage medias and programs. You will find the models for each entity along in the sections below.

A media has a name, a file, a duration, and a description.

• Create a media (don't upload anything for real, just create a fake audio file or use a dummy URL)
• Edit a media
• Delete a media
• See all the medias on a page (with pagination)

A program has a name, a cover image (you can use a dummy URL), and a description.

• Create a program
• Edit a program
• Delete a program
• See all the programs on a page (with pagination)

• A program can contain between 0 and infinity medias.
• A media cannot be in more than one program.
• The order of medias may matter.

• You must use the boilerplate code as a base for your work. You can add any other dependency you need.
• You must deliver all the features required.
• You must test your endpoints to make sure they work as expected. How you test them is up to you.

• You can add any extra feature that you'd like to see in this app. Be creative!
• You can also add any extra quality of life improvement to the app or code (linter, formatter...)