Note: it will be easier to review this after #35 gets merged in because this was built off of those changes
This is to simplify our API (not to be confused with the ProdOps API) that we're exposing to users. The attempt is to:
get rid of duplication by removing the wrapper functions that made up lib/prodops_ex.ex, since these were really just functions calling other functions
standardize the naming conventions so that we use the verbs list, get, create, and delete for CRUD operations (we may be adding refine or similar to these?)
move away from maps for the parameters for list, get, and delete in favor of explicit params
Links to #31
Note: it will be easier to review this after #35 gets merged in because this was built off of those changes
This is to simplify our API (not to be confused with the ProdOps API) that we're exposing to users. The attempt is to:
lib/prodops_ex.ex
, since these were really just functions calling other functionslist
,get
,create
, anddelete
for CRUD operations (we may be addingrefine
or similar to these?)list
,get
, anddelete
in favor of explicit paramsAs an example, before this was:
ProdopsEx.Artifact.get_artifacts_for_project(%{artifact_slug: "story", project_id: 1})
Now it looks like:
ProdopsEx.Artifact.list_project_artifacts(1, "story")