habitica | habit tracker app which treats your goals | Runtime Evironment library

A POST always has a payload (content). A POST without content is unusual, so are you sure you didn't forget something?

You need to call setEntity() to set the payload, even if it is empty, because it is the entity that sets the Content-Length header.

E.g. you could call httpPost.setEntity(new StringEntity("")), which sets Content-Type: text/plain and Content-Length: 0.

You could just make a template string and format it like,

Is it a browser modal or a modal developed by your team? In the first case Cypress should automatically accept the modal. In the second case you can work around it by only accepting it when it is visible. You can do that by adding this to your script:

Since this is very broad I am going to give you high-level answer. The individual desktop clients all share the same database (MySQL).

Therefore, you can solve this problem there: in your database.

One option would be to have a some kind of "group task". Every user of your app can sign up for this task and when it is "completed", everyone earns some points.

To manage this you could have to tables in your database:

• One table for the tasks
• One table for collaborators

Every task needs a unique id that you then can reference in your collaborators table.

Your assumptions are correct.

Vue events were borrowed from AngularJS, event API changed further in Vue 2. The concept is similar to DOM or other JavaScript event implementations:

Note that Vue’s event system is different from the browser’s EventTarget API. Though they work similarly, $emit, $on, and $off are not aliases for dispatchEvent, addEventListener, and removeEventListener.

Siblings should communicate through common parent, $root instance acts as global event bus. Event listener is registered inside one component and is triggered inside another one.

Each user would have a collection, probably with their userID as the name of the collection.

While it is possible to dynamically create a new collection for each user, I would not recommend doing this because any collection-specific settings (like indexes) would have to be duplicated and kept up to date across all collections. Instead, I would create a single collection, use a property like userId to store which user a document belongs to, and speed up database queries by creating an index on that property.

If you're not familiar with indexes, they're basically a way of saying "I'll often query based on this property, please note down the values of this property separately so they can be accessed more quickly".

The only thing I have tried is looking up different ways of doing authentication, but I would like some guidance on where to start

An approach that is fairly popular with this kind of stack is using JSON Web Tokens. Here's a quick overview of how you would implement these in your application:

1. Come up with a sort of password to securely sign the tokens. This can be a string of random characters. Store it somewhere your Express application can read it from (for example a .env file). This is your key.

2. When a user logs in from your Vue.js front-end, a request is sent to your Express back-end to validate the username and password (make sure to store passwords securely with something like bcrypt). If the credentials are correct, you can create an object containing the user ID and additional information you might want to use on the front-end (e.g. { id: 'myuserid', name: 'John Doe' }). You can then create a token with the object as the payload and your key and return it in the response to the request.

3. The front-end can now store the token as a cookie or in localStorage and from then on attach it to every request through a header. Since you're planning to use Axios, this is how you'd do that:

This comes from the i18n : https://github.com/HabitRPG/habitica/blob/develop/website/client/libs/i18n.js

It looks like without the leading dot, pug renders a component

I don't know Pug well, but it seems to me that the pasted Pug code creates a menu-dropdown element with those given attributes. right attribute is bound to a dynamic value from the Vue model using the v-bind: directive's shorthand :.

I searched for menu-dropdown component's definition in the repository you linked, and find this file: https://github.com/HabitRPG/habitica/blob/develop/website/client/components/ui/customMenuDropdown.vue

This is where the right attribute is defined as a Vue prop: