The objective of this project is to learn graphql query language by creating your own profile. It will be provided,\
The objective of this project is to learn graphql query language by creating profiles. It will be provided,\
by the platform, a graphql endpoint that is connected to the database. So you can query this endpoint to obtain the information you desire.\
**Note** that for security reasons some tables are private and some are public, you will only be provided with certain content.
@ -23,7 +23,7 @@ GraphQL is a query language for any API endpoint and runtime. The syntax lets yo
You must have in mind that this language is used for API endpoints and not database. Unlike SQL,\
graphql query does not go to your database directly but to your graphql API endpoint which can connect to a database or any other data source.
You are already familiar to REST, since REST is a robust methodology of creating APIs and not elastic/scalable.\
You are already familiar with REST, since REST is a robust methodology of creating APIs and not elastic/scalable.\
It can be at the same time painful, because it requires individual creation of each API, example: `v1/user/item/{id}`, `v1/post/item/{id}` and so on.
The main feature of graphql compared to REST is that it lets you ask for specific information. And even better then that is the nesting feature.
@ -65,62 +65,95 @@ query {
}
```
For this example we ask for the users followers and request their names and ids.\
The examples above are simple examples, **note** that this query is require the introduction of variables(arguments)\
For this example we ask for the user followers attribute, requesting the followers names and ids.\
The examples above are simple examples. **Note** that for this query is required the introduction of variables (arguments)\
so it will return just one user, the user that as the id equal to `13`.
In graphql the usage of arguments can be specified in the schema of the API endpoint. Here is the *docs* for the graphql endpoint you are going to use, [Schema](https://01.alem.school/public/subjects/grapqhl)
In graphql the usage of arguments can be specified in the schema of the API endpoint. Here is the _docs_ for the graphql endpoint you are going to use, _https://[[DOMAIN]]/public/subjects/grapqhl_
<!-- EXPLAIN WHAT IS GOING TO HAPPEN -->
---
### **profile**
You will have to create a profile system where you can see all the info of a student. The information/data is present\
on the graphQL endpoint, where you will have to query it.
The display of the information is up to you to design, but it must include:
- Basic user identification, for example **githubLogin**
- **XP** amount
- **level**
- **grades**
- **skills**
- **statistics**
Any other information you desire to display is welcome and will be noted
Beside this information, you will have to create a search engine which returns a selection of students profiles, based on the students:
- Name
- XP
- level
- skills
For instance you can search for a student by their `githubLogin` or filter the students by the amount of `XP` or which `level`/`skill`.
---
### Usage
> Here are the list of tables that you are available to query:
> Here is the list of tables that you are allowed to query, for more information you can check out the _docs_`https://[[DOMAIN]]/public/subjects/grapqhl`:
