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

Add bike goal list view and routes #207

Merged
merged 11 commits into from
Oct 12, 2022
Merged

Add bike goal list view and routes #207

merged 11 commits into from
Oct 12, 2022

Conversation

JF-Cozy
Copy link
Contributor

@JF-Cozy JF-Cozy commented Oct 12, 2022

Grâce à une nouvelle route, on accède à une nouvelle page qui liste les trajets
de l'objectif vélo, ainsi que la progression de l'objectif.

Pour l'instant ce n'est que sur l'année en cours.

La requête réel n'est pas encore exploitable (une autre tâche préalable est
nécessaire), on requête dans cette PR tous les trajets de manière classique en
attendant.

### ✨ Features

* Add bike goal list view and routes

@bundlemon
Copy link

bundlemon bot commented Oct 12, 2022

BundleMon

Files updated (3)
Status Path Size Limits
vendors/coachco2.(hash).js
649.39KB (+4.9KB +0.76%) -
app/coachco2.(hash).js
40.66KB (+1.12KB +2.82%) -
vendors-coachco2.(hash).(hash).min.css
32.46KB (+32B +0.1%) -
Unchanged files (1)
Status Path Size Limits
app-coachco2.(hash).min.css
140B -

Total files change +6.05KB +0.84%

Final result: ✅

View report in BundleMon website ➡️


Current branch size history | Target branch size history

@JF-Cozy JF-Cozy merged commit fe58810 into master Oct 12, 2022
@JF-Cozy JF-Cozy deleted the feat/BikeGoal branch October 12, 2022 12:57
import { countDays } from 'src/lib/timeseries'

export const getDaysToReach = () =>
flag('coachco2.bikegoal.settings').daysToReach
Copy link
Contributor

Choose a reason for hiding this comment

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

Dans l'état, on a une erreur si le flag n'est pas défini.
Peut-être qu'on aurait pu mettre une valeur par défaut ou émettre une erreur explicite dans ce cas ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

exact, je me suis posé la question, et je suis parti du principe que de toute façon l'app ne marcherait pas sans et que le flag serait présent sur les instances... un throw explicite serait bien dans ce genre de conclusion 👍

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.

3 participants