It is urgent to finalize the article parser. There are some errors and inaccuracies in the implemented code, here is the code:
https://github.com/0-EternalJunior-0/-autonewsparser
There is a more up-to-date version in archive format (the developer started, almost finished, and then disappeared, and the deadlines are tight, it was supposed to be submitted the day before yesterday of the last month), I will send it in a private message. It may be necessary to fix a few bugs there, and everything will work as we need.
More details - in a private message. But just in case, below is the original task for correcting the above code (in the archive, part or most of this may already be done).
New necessary API commands:
1.
A command is needed to request N articles by 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, the 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 where parameters 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 DB 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… do not remove any fields from the response, return all that exist
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 set parameters 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 DB 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 went 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.
