Merge pull request #1969 from gustavomm19/refactor-common

Refactor of services, hooks and Checkout

Author: tommygonzaleza

.cursor/rules/auth.mdc

@@ -0,0 +1,9 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+The authentication of the user is managed through the [AuthContext.jsx](mdc:src/context/AuthContext.jsx). This context provides the basic functions to login, logout and validate the current session.
+
+
+To get information regarding the authentication and the user we use the [useAuth.js](mdc:src/hooks/useAuth.js) hook, which consumes from the AuthContext.

.cursor/rules/components.mdc

@@ -0,0 +1,21 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+##Components
+All of our components are in the folder @/src/components. The files and folders names must be created using PascalCase.
+
+###Icons
+We have an Icon component inside the components folder. The Icon has a set of icons inside that folder, which are svg components that can be customized with props (width, height, style, color, etc.).
+
+###UI Library
+Our UI library is Chakra UI. Whe should always use Chakra to build our pages and our components.
+There are some chakra components that are customized with our own styling, so we should use those instead of the ones from chakra:
+- src/components/Text
+- src/components/Heading
+
+###Styling
+We have all of our colors defined on the theme.js file inside the styles folder. We must always use the color variables declared in that file.
+
+We also have the useStyle hook which has color modes declared with our defined colors. The object hexColor can be used with the icons, since the icons dont support the color variables natively through strings.

.cursor/rules/good-practices.mdc

@@ -0,0 +1,11 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+##Promises
+When using promises we wont use the chaining event syntax, we will use async/await and try/catch to avoid the callback hell.
+
+##Linting
+
+We are using ESLint to improve the higene of our code. Make sure to follow its recommendations and fix linting errors if they arise.

.cursor/rules/lib.mdc

@@ -0,0 +1,6 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+In the lib folder we are storing functions that reuse calls to the API and dont involve hooks.

.cursor/rules/services.mdc

@@ -0,0 +1,10 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+##Breathecode
+The service breathecode is the api from where we will consume most of our data. Every time we want to communicate with breathecode, it must be done using the service declared in the [breathecode.js](mdc:src/services/breathecode.js) file in the services folder. Internally, the breathecode service is separated by modules, which corresponds to the modules of the api.
+
+##Rigobot
+Rigobot is another api from where we will consume some data ocasionally. This service is also structured by modules inside the file [rigobot.js](mdc:src/services/rigobot.js).

.cursor/rules/subscriptions.mdc

@@ -0,0 +1,6 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+The subscriptions of the user are managed through the hook [useSubscriptions.js](mdc:src/hooks/useSubscriptions.js) and they are loaded after the user is authenticated.

.cursor/rules/utils.mdc

@@ -0,0 +1,6 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+In the utils folder we will only store pure functions that are reused in may sections of the project