drewromanyk / glamrous.me Goto Github PK

Anything with multiple assignees is not being counted because you have to pull from a different field in the GitHub API results

• create IDB1.log

• Quality of unit tests
• 10 to 15 tests
• run coverage
• coverage results

Tests can't be run yet

2500 word report

I think https://gist.github.com/Rich-Harris/cb14f4bc0670c47d00d191565be36bf0 has some details on Rollup setup to make that happen.

• fd6cb3d
• 1d44489
• 5204258
• dacc970
• 1cde78b

• 3 full instances for each model

When stats need to be recached on Github's side, we get back status code 202, and are instructed to wait a few moments and try again. We don't handle this right now, so sometimes the stats just don't update right and the page must be refreshed

• Needs at least 15 issues

• get approved

jsxstyle: https://github.com/smyte/jsxstyle

• Quality of API

Doesn't need to be implemented until next phase

• put on about page

• About Page
• Design, Asethitics
• Embedded Media,
• Links from models to models
• Easy to navigate, no broken links
• Grid, filtering, sorting

(in the frontend)

• Context
• 10 results per page
• Add to report

• pydoc for app/models.py
• create inline comments if you need to explain why for a implementation

Woops, forgot about this part of the page

fill database with makeup api

I know someone did this last section, but I don't remember who. Assign yourself and close this issue for a free +1 on your stats on the about page! :D

So that, e.g., instead of

<div className='container'>
    <div className='row'>
        <div className='col-lg-4'>
            {...}
        </div>
    </div>
</div>

we can have

<Container>
    <Row>
        <Col lg={4}>
           {...}
        </Col>
    </Row>
</Container>

Instead of manually updating every push to master, because that's awful

• app/tests.out
• run coverage
• coverage results

We forgot last time I think...

• Quality of models
• assertions
• pylint results
• autopep8

• Update Apiairy
• Update Tech report API section

• Finished

• 3750 words
• use cases, RESTful API, models, tools, hosting, and DB
• good sections, multiple pages, good headers, figures, and grammar
• table of contents ( #36 )