pjbehr87 / space-traders Goto Github PK

Right now all of the waypoints are returned in a flat list of all waypoints in a system.

Improve this list so that orbital waypoints are returned as children of the waypoint they orbit. Maybe add some expand/hide functionality to the page so that orbitals show their type, but can be expanded for more info.

https://docs.spacetraders.io/quickstart/purchase-ship

Add the ability to click on the "SHIPYARD" trait of a waypoint a view the inventory of said shipyard.

There are 2 cases where automatically creating an agent can happen:

1. The config file doesn't exist. From here we ask the user if they already have a token/name or if they want to automatically create a new agent. Walk them through either, then inject the name/token into a new config file which comes from the template.
2. The config file exists, but the token field is empty. Same thing as above, ask if user has token or wants to create account. But, this time inject into existing config so the user doesn't lose any changed configuration.

To do this, there are multiple options:

• Change the GetConfig function to return the error, and have logic for handling the error in main. This way we don't have to pass the stapi to the Getconfig function when 99% of the time this isn't used
• Init stapi above GetConfig and pass the apiClient to GetConfig, so that in this case the GetConfig function can handle the new agent stuff

Either way there is a lot of overlap between the new agent stuff and should be handled in functions in the newly named internal.go file.

https://docs.spacetraders.io/quickstart/purchase-ship

From the shipyard page, you should be able to click a button to purchase a ship.

Most likely this will be an AJAX call to the purchase ship endpoint. After the AJAX call we can redirect to the "my ships" page. Possibly highlight the just-purchased ship with a URL param.

The shipyard view is really messy because ships have so much data. Figure out a way to trim down or hide, by default, some of the data.

The README should have instructions on how to run the project

This should include the ability to load a home page that asks for an Agent name then creates a new one, including populating the config file.