Many algorithms in Project Euler do not follow coding styles as mentioned by @dhruvmanila here, or even the standard coding guidelines.

Notes:

• A lot of inconsistencies with the solution functions (a lot of them aren't named as "solution")
• docstring inconsistencies:

>```docstring```
vs
>```
docstring``

Add a new schematic to generate:

A service that extends ComponentStore
A spec file if requested
Maybe an inlined interface for the default type

Describe any alternatives/workarounds you're current

Behavior of the program
When I hover over the volume and try to adjust it with the scroll wheel it just scrolls the page. I've read in a closed issue that this feature was supposed have been implemented.

Expected behavior
Hovering over the volume and using the scroll wheel should increase/decrease volume.

To Reproduce

1. Open video
2. Hover over volume bar
3. Scroll up or do

The current website, does not have any default Favicon. I can add this, if you'll assign this issue to me.

Summary

The existing docs about adding Google analytics recommend using the gatsby-plugin-google-analytics. Under the hood, this plugin uses Google's analytics.js file.

However, Google has a guide recommending users upgrade to gtag.js instead. There

🚀 Feature

Implementing the Algorithm to find the Diameter of a Binary Tree

Have you read the Contribution Guidelines?

Yes

Assignees

@musaabshirgar1 - Kotlin
@Sudheer121 - C++
@0utplay - Java
@arnav-roy - Python
@yashkansal - C
@DemonDaddy22 - JavaScript
@cr33dx - Golang

Problem

#6909 is a PR, abandoned by the original author, that made bytestring = fig.savefig(None, **kwargs) equivalent to import io; buf = io.BytesIO(); fig.savefig(buf, **kwargs); bytestring = buf.getvalue() which