msscsh / brawlstars-crawler Goto Github PK

This functionality should allow the inclusion of points obtained by each player during the league. These data can be stored in a relation file, similar to those used in the other functionalities. The points/player ratio must be guaranteed by the player's tag.

Steps:

Rules:

Create a external param that could increase the log level os the python application

When http code is 500 should store the player's tag and then search him before.

• create file with tags
• search
• remove file

Save current player position too make action later

should use venv so the project can be portable

The club league has been changed. This way, it would be an option to rebuild the project. Designing the new solution based on the Mega Pig update.

Create battlelog feeder to all club members from one club tag. Should store the club member in document and add all of then to the updating routine of battlelog.

When adding a new player, some process must be carried out. This way we can get a consistent basis. Are they:

• Calculate wins and loss (limited to api 25 lenght history)

When the oficial API is consumed, the name "items" is been passed. But acctualy should use the list name "BattleList", "ClubMembersList"...

create a feature to count brawlers' information

create a feeder to walk over a taglist id's and call update functions

count the times that someone is holding first place. It must send the time to the front so that it can follow the count like a clock.

create routine for backup all data in project

It is necessary to create an execution scheme using Docker containers so that it is possible to perform restart procedures on the application as a whole

There must be a module that has the rules to be observed when counting points in battles. This way it is possible to remove responsibilities that are being embedded within the battlelog feeder

You need to create a module with EJS that allows:

Steps

Expected steps for the execution of the functionality by the user

• 1. Navigate from the home screen to the teams functionality
• 2. Allow changing/including team members
• 3. At the end, generate the file "team_relation.txt"

Rules:

• The screen must be loaded with the existing "team_relation.txt" file, if it does not exist, a new file must be created.
• The player data that will be used to make the relationship will be the ones in the "master.json" file.
• Tags of players who are no longer in the club must be removed from the team relation file(team_relation.txt) when the player's absence is identified in the main file(master.json)

We need to define specific types to be used in the application. For this it is important that the places where ESLint is ignoring are reviewed. Locations ignored and in need of revision include the following line:
// eslint-disable-next-line @typescript-eslint/no-explicit-any

must complete with empty lines when there is not the total number of members

today the normal game mode is counted based on the exclusion of all other types, which causes other types of games not mapped and without the "result" field to interrupt the battlelog feeder process

Create functionality that allows you to "cut" the score according to date. You must scroll through the battle records and filter according to date. This clipping should be used in the player audit to obtain a time score. With this construction it is possible to separate the top players at a given time.

When a player ceases to be part of the club, he should be disregarded in future consultations regarding his departure

create a functionality that allows the presentation of information relating to a ranking.

Create base for test the application, python and shell

Currently, rounds are counted and not the final result. Star player only appears in the last round

create a procedure that allows you to report the time that the crawler remained online and offline, as well as the time that each player was not monitored due to error 500 from api

When consume the oficial API should remove the information: "paging"

When the fedder is crawling, sometimes the api start to sendo HTTP Error 429. It must be handled so that the crawler does not miss a record to be searched. This treatment can be a new attempt after x times, like a system pause

It must transform the json within the debugger, avoiding the need to import the "json" by other modules

The attribute functionality opened up a wide range of field possibilities. Possible attribute values can no longer be loaded indiscriminately, so they are loaded directly from a combo box

create a mechanism for consuming official APIs with high supply. It must allow consuming the minimum player, club and team services.

The results must be persisted in json files or NoSQL database

include score field in players ranking

Typescript's compilation process is ignoring the "include" settings described in the tsconfig.json file. In this way, it is necessary to use the "copyfiles" dependency to perform the copy, in a "hardcode" process.
The typescript build must respect the settings in its own configuration file.

create one file util to center thing

when during processing the program tries to save the player's link status with a club. In this feature, for some reason, the field value is not stored.

return club role with emoji in html_creator

The pipeline process in package.json is running wildly. The returns from each of the steps must be analyzed so that the process does not end up as a false positive.
Currently, when errors occur in the generation of keys for the API, the build is completed successfully.

when in the middle of feeding the feeder, errors may occur. Identified were "429" and "Temporary failure in name resolution". Regardless of the error that occurs in the middle of the process, the system must understand the point at which the failure occurred and subsequently resume

when the mode is "big game" an error occurs in counting points which causes the process to be interrupted

Add rules that allow you to create a daily ranking. The players who managed to achieve these objectives can be displayed on the first screen. This scoreboard must be made available at midnight and counted throughout the day in the feeder's central process.

• Most wins
• Most defeats
• Most points
• Most rounds in PL

When a player is already added to the database, their data is not updated. When updating battle data, or in another process, other information must be updated: Number of trophies, nickname...

The routes must be kept in different files aiming at a better structure of the application. For this it is necessary to "inform" express which files will be used, as well as a way to separate the use.

When assembling teams, it is impossible to identify the attributes of the players, only their nick. It is interesting that other profile information is presented, so that during the escalation process these values can be used for an analysis.

change cypress to selenium

The solution of reprocessing in case of errors is not the best way. It is necessary to act at the OS level. It will be necessary to notice the creation of the error file and then trigger the steps to revalidate the key for the API.

show players nick in logfile when running the routine

should allow the counted information to be recalculated through your battle history

This functionality aims to search for the registered telephone number for the player through its tag. The data should be kept in a separate file, similar to "team_relation.json".

Steps:

• create EJS screen
• Generate file with number relation

Rules:

• Must load the screen data from the file "number relation.json".
• If the file "number relation.json" does not exist, a new file must be generated.
• The file "number relation.json" cannot be versioned

It is necessary to carry out a design project for the pages, so that there is beauty associated with UX. It is necessary to make definitions of colors, layout, borders, buttons and other elements that make up the pages.

Apply standard formatting to all files.
Preference should be given to the use of tab.
If possible, add control tools so that formatting is respected in one of the build processes