Project: SQL Zoo: No need for community solutions

[dilpreetsinghaulakh]

Checks

• [X] This is not a duplicate of an existing issue (please have a look through our open issues list to make sure)
• [X] I have thoroughly read and understand The Odin Project Contributing Guide
• [X] Would you like to work on this issue?

Describe your suggestion

SQL Zoo is solved in the browser so there is no need for community solutions as there is no obvious way to share the solution.

Also, "feedback form for the SQL course" leads to (says) ruby on rails form even in NodeJS path.

Path

Node / JS

Lesson Url

https://www.theodinproject.com/lessons/node-path-databases-sql-zoo

(Optional) Discord Name

No response

(Optional) Additional Comments

Just small discrepancies!

[wise-king-sullyman]

Thanks for submitting this issue!

I fixed the google form issue since that requires admin access to our gforms.

For the SQL Zoo lesson submissions I believe that change requires an update in our site repo, specifically of the accepts_submissions key for the lesson in its fixture file, so I'm going to transfer this issue to that repo.

Are you still interested in making that change?

[dilpreetsinghaulakh]

I think it can actually stay as I have just seen a submission in which the submitter put the solutions for SQL Zoo in a repository. Although I still don't think it is the best implementation here.

[MaoShizhong]

I feel like user submissions isn't really that relevant here given the SQLZoo exercises are marked right or wrong when you do them. So I'm in favour of just removing the submissions component for that lesson.

[Asartea]

Agree with Mao that there is no real point to storing these, since there is already build in checking

[MaoShizhong]

@dilpreetsinghaulakh Are you still happy to be assigned to this issue and change the accepts_submissions value to false as per wise-king-sullyman's comment above?