Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix badge date 248 #278

Merged
merged 7 commits into from
Jun 7, 2019
Merged

Conversation

adamzev
Copy link
Collaborator

@adamzev adamzev commented May 26, 2019

Status:

Deploy link

Description

badges are labeled with current year

Using the db table Year which stores a single value (what the current year is) the badges will display the current year.

Note: there may be a need to store these badges in the database rather than calculate them on the fly. The way this is designed will likely produce undesired results when switching the program from one year to the next however for demo purposes, the current method should work.
Related issues: #248

Todos

Screenshots

Adam Levin and others added 7 commits May 11, 2019 12:43
* added to .gitignore
* added a file testdb_seed
* removed reseting db from docker_script because this is handled in docker-compose-dev

NOTE:
docker-compose.yml is not currently used and will not reset or seed the database.
Just use docker-compose-dev.yml for now.
requests: 2.18.4 > 2.22.0
SQLAlchemy 1.1.14 > 1.3.3
PyJWT 1.4.2 > 1.7.1
urllib3 1.22 > 1.25.2
alembic 0.9.6 > 1.0.10
flask-sqlalchemy 2.3.2 > 2.4.0
pyscopg2 2.7.5 > psycopg2-binary 2.7.5
sqlalchemy-utils 0.33.5 > 0.33.11
werkzeug 0.14.1 > 0.15.4

Specifying a jwt decode algorithm avoids a deprication warning that would have been introduced from these version update commits.w
requirements.txt is generated by pipfile so fixing pipfile should have been the first step. This commit should fix the outdated libraries that had security issues.
Using the db table Year which stores a single value (what the current year is) the badges will display the current year.
Copy link
Collaborator

@codenprose codenprose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, I think this is fine for demo purposes. @tutordelphia when you get a chance I would just create a separate issue outside of the MVP project that captures what work should be done prior to an official v1 launch.

@codenprose codenprose merged commit 8f7f449 into hack4impact-uiuc:master Jun 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants