Oh Oh Bug!

GIF
No Bugs!

What we worked on

Pictury:

1) When a user made a query that didn't return any result, the extension was throwing an error message in the console and nothing was informing the user of the problem. We implemented a "No Results Found" message and a handle for the error that was thrown.

2) The old shortcut used to open the web view was causing a lot of conflicts, so we modified it for another one ("SHIFT+CTRL+P"). We also added the option to open the web view by right-clicking anywhere in VS Code and going to the pictury submenu.

3) Reviewed the work of another team that was contributing to Pictury, and that added a clearer notification that appears on top of an image when the user copies or downloads the pictures. They also added a credits section for each picture.

4) Updated the README.md and released the new version of Pictury

Search-Savior:

1) The date of each new item/search group wasn't being stored: we fixed that by storing each item's creation date in the chrome storage.

2) Added documentation for the directory structure on what the files are doing and handling stuff. Also tried to present how the files are interconnected to each other.

Technologies we used

JS
HTML
CSS
MARKDOWN

Challenges we ran into

1) Ramadan started this week, and I (Ali) was fasting since Tuesday. The first couple of days were hard and I couldn't contribute much, but I tried to make up for that during the second half of the week.

2) The CTF Challenges took us time to complete (especially the Laila challenge)

Accomplishments that we're proud of

1) We ended up publishing the second version of "Pictury" (A VS Code extension we worked on previously)

2) We collaborated with a team from another pod and worked together on Pictury

3) Solving the Laila CTF Challenge (this may not be very relevant, be it was the best moment of the week so we had to add it in here)

What we learned

1) We understood the value of having clean, well-structured, and well-commented code when we tried to work on our previous projects and found ourselves struggling to understand our own code.

2) How GitHub issues work, and the different labels you can use

3) How to contribute to open-source projects in a proper way (Forks, PRs, etc...)

4) Reviewing the PRs of other teams on our projects' repositories and giving useful feedback