arkultur / naboo Goto Github PK

Think of the Versailles castle, it has one address but multiple points of interests.

We should be able to embed many nodes in an Address object

Teams should be able to "own" addresses and nodes

Currently, these are serialized in HTML. Unfortunately, as an API, this suck. we need to fix this

lol /api/maps/address [POST] no work

https://stackoverflow.com/questions/54066733/how-to-accept-json-in-absinthe-graphql-requests?rq=1

-> This should be done by removing the naboo_web/ directory

need to fix ci as well

• improve unit tests with bearer token for account_controller
• implement Bearer Token auth for grahpql queries

Following the logic of this file, we can maybe add some data for nodes, addresses and stuff for the presentation, so that the integration can be smoother

• Hotel Dieu, Lyon
• Place Bellecour, Lyon
• Tour Eiffel, Paris

we should add a magic test route (only available for test and dev which will set the current user as admin)

implement:

• coveralls
• ExUnit
• attempt to run migrations to see if all is working

add a setup.sh and nuke.sh script for dev-env setup

The information provided is not sufficient to know where the tests are lacking.
We would need an HTML page auto-generated giving us precisely what lines are executed.

You willl need to research this, as I don't have the time to do it currently.

• controller for Address
• tests for address_controller

We have a couple of TODOs in the codebase regarding that issue.

Basically, we want to ensure the data persisted is "real", here is some useful information on validation, however i am not aware of any regarding geolocated fields, so you will have to research that.

-> Notes on the GeoJSON format

• Describe #43 in README and usage for front-end and mobile users
• describe how to run tests, get dependencies and build locally
• describe expected data (OSM geo-located data)
• fix parameters in swagger

• a successful push to dev should do :

docker tag naboo:${VERSION}-dev bogdzn/naboo:${VERSION}-dev
docker push bogdzn/naboo:${VERSION}-dev

• a successful push to canon should do :

docker tag naboo:${VERSION}-dev bogdzn/naboo:${VERSION}
docker push bogdzn/naboo:${VERSION}

we will of course have to properly manage docker credentials

Push conditions are not properly working currently (should only trigger on canon and dev but triggers on every branchs)

• build and push docker images when releasing to the main branch
• build and push docker images when releasing to dev branche (with MIX_ENV set to dev)
• update github actions
• add new dockerfile with dev MIX_ENV