Hello, there is a parser, here is its code:
https://github.com/0-EternalJunior-0/-autonewsparser
The developer has disappeared somewhere, and we need to make changes to it. First of all, ensure that it is set up to automatically parse news based on a given criterion, because right now it seems that parsing is initiated only on command. If auto-parsing is not set up, it needs to be configured. The project is deployed on our server, and we will provide access to the executor.
Secondly, here is a list of tasks (for improvement) from our developer regarding the API:
---
New necessary API commands:
1.
A command is needed to request N articles based on an arbitrary WHERE query
it can be named anything, type POST
input data:
{
“where”:{
“field1”:”value1”,
“field2”:”value2”,
“field3”:”value3”
},
“limit”:10
}
the limit value can be anything, but it can be restricted to something, for example, 100… if limit is not provided - return 1 article (by default)
in where any fields can be passed, values are written in string (for universality)... I hope “1” and 1 when querying the database will be considered the same value and will not cause an error… before forming the query, all passed parameters in where need to be checked for existence in the table, for example, using
SHOW COLUMNS FROM articles
or
DESCRIBE articles
and if any field does not exist, return an error
based on the data, a query to the database is formed like
SELECT * FROM articles WHERE field1=’value1’ AND field2=’value2’ AND field3=’value3’ LIMIT 10
all WHERE parameters are combined using AND
and all results with all fields are returned in the API request response… there is no need to remove any fields from the response, all that exist should be returned
2.
A command for arbitrary editing of an article by id is needed
it can be named anything, type POST
input data:
{
“set”:{
“field1”:”value1”,
“field2”:”value2”,
“field3”:”value3”
},
“id”:1
}
before forming the query, all passed parameters in set need to be checked for existence in the table, for example, using
SHOW COLUMNS FROM articles
or
DESCRIBE articles
and if any field does not exist, return an error
it is also necessary to block the transmission of id in the set section, and return an error if id is found there
“set”:{
“id”:”2”
},
this is a clear error, id cannot be changed
based on the data, a query to the database is formed like
UPDATE articles SET field1=’value1’, field2=’value2’, field3=’value3’ WHERE id=1
in the API request response, it is enough to return a 200 code for a successful operation, and another code with a description of the error if something goes wrong
IMPORTANT:
I will be adding fields and indexes to the articles table, so both commands need to work with any fields, current and future, and not be limited to the current table structure.
---
Thirdly, it is necessary to figure out how the delete command works, whether articles that were deleted by the command will be parsed again.
