yathartha22 / notices-api Goto Github PK

No need to check this field in the api we will check this in front end.
Right now api is throwing an error for confirm password:
{"confirm_password":["This field is required."]}

Codebase should be cleaner and docstrings and comments should be included so that it becomes easier to understand for a third person.

added author's image url along with notice details. Committed directly to master.

@shubham9411 have a look.

We can currently create notices and read them. But some operations like Update and Delete are not available yet. Update and delete operation are also important if the user created wrong notice or mistyped or just wanted to delete them.

I have added a notice from my id when I again added another notice then the server crashed and was giving some kind of IntegrityError. I am adding image as attachment.

I have added user story in the issue here. Let me know when API will be ready.

If we send null as a param in any of the api year/branch or both it returns data for others because the value is null for them.
Example: Post year:null in http://localhost:8000/api/v1/notices/year/ it will return all data for branch and all. It's a Bug that should be resolved ASAP.

A functionality needs to be added for certain users(admins) to create, edit and publish notices.

After the new pull all the published dates are disappeared from the frontend. APIs are not returning the published date of the notice. Is it a new design decision or any issue with the code?
Please check this ASAP.

After registering a user api does not send jwt token as the response. please check that

If we leave any field blank it is sending an api response like this:

{
  "password": ["This field may not be blank."],
  "username": ["This field may not be blank."]
}

can it be changed to something like:

{
  "password": ["Password field may not be blank."],
  "username": ["username field may not be blank."]
}

My question is, is it possible?