This repository hosts the beta implementation of the Urban Online ES Workflow. The project is intended to give urban planners the ability to create and assess scenarios using InVEST Urban models.
1
stars
5
forks
source link
Use consistent names for endpoints and associated functions #51
We have different names for functions and associated endpoints at different places in the code: functions in requests.js that call endpoints that call functions in main.py that call functions in crud.py (also maybe some schemas). Let's use consistent naming:
sessions and users are the same thing for our purposes, but we'll refer to them as sessions.
POST /users should be renamed to /sessions or similar
look up: is there a convention for naming endpoints that could be singular or plural? (scenario vs scenarios, job vs jobs)
consider doing away with getScenario
choose between "fill"/"parcel fill" and "paint" - "fill" is probably more conventional
We have different names for functions and associated endpoints at different places in the code: functions in
requests.jsthat call endpoints that call functions inmain.pythat call functions incrud.py(also maybe some schemas). Let's use consistent naming:/usersshould be renamed to/sessionsor similargetScenario