eraldo / colegend Goto Github PK

As a developer, I want obsolete code and dependencies to be gone from the current codebase, so that I have less code to maintain and make it easier for other developers to grasp what is going on.

Model candidates:

• Currently unused page models.
• Biographys
• Guide relations
• Inner calls
• Outer calls
• Visions
• Waiting users

Misc candidates:

• template related stuff (template tags etc)

I want to remove them with confidence, since I have the repo to timetravel in case I want to look back. When it comes to content, I will update relevant data in drive storage.

As a content writer, I want to be able to write content pages in wagtail cms and have the result including links to other pages show up in the frontend, so that I can relate from one page to another and include images.

Right now I can get the value of each streamfield block, which depending on the field may be an image id (in django format) or html in case of rich-text.

The problem is that the rich-text includes wagtail created links that do not work for my frontend.

Solution idea:

• writing a converter for the stream blocks in the backend and an interpreter for the frontend.

As a user, when I have completed a quest, I want to get a message congratulating me in text and sound (if enabled), so that I feel positively rewarded for my effort.

Outcomes:

• Quest completion mechanism
  • Text message
  • Experience gain
  • Completion sound

As a user, I want to be able to know when my streak will reset and have that happen at my local time, so that I do not have to calculate when my streak will reset depending on where I am, since that means adjusting my timed habits which kind of defeats the purpose of building consistent habits.

Current implementation:
reset is happening at 4h server time for all users.

Solution idea:

• Adding timezone field to users.
• Running job every hour and processing only effected users depending on timezone.

Future improvement:

• Using cellery instead of crontabs (scaling)

As a developer, I want to be able to define limitations on which model instances can be fetched by a DjangoFilterConnectionField even if queried indirectly as a reverse foreign key relation of another model.

Currently my filters only apply where I explicitly set them via DjangoFilterConnectionField -- not on related entry points.

I saw some code from stephrdev which would fix this. With the comment that it would probably not work as is in my repo.

stephrdev: Can you please point me to code again?

As a user, I want to be able to login into the app without relying on local storage, so that I don't have to keep information in my local storage and don't have doubts about security concerns.

I tried enabling session login. I am calling django's login method, however the frontend does not seem to act accordingly.

hypothesis from @stephrdev: A new session is created that is sent back to the caller, however the frontend still keeps using the old one.

What to do? Where to look next?