Great progress. As your first foray into Discourse plugin dev, this is definitely ambitious. The upside of that is the sense of achievement and utility you will get once you get this working. The risk you run here is you are biting so much off in one go it might put you off continuing to work on the platform. The Ember/Rails combo is quite a lot to take on, especially initially, keep going!
Some tips for the time being:
- Tackle things in chunks.
- Pushing the fork to GitHub, then permalinking sections of code here might help the community see what you are doing more clearly.
- First worry about the down data from your Rails controller, check that by addressing the rails route with
.jsonon the end of the http address to see the raw data that is being passed down to the client. That will prove out the Rails side of the GET. - Think of the Ember Controller as the module to handle “in interface actions” and stuff that might have to be pushed back up to the back-end (You can handle actions on Routes too, but I digress! :D)
- The Ember Router connects the back-end to the rest of the front end, setting up the model for the Template, it’s Components and/or Controller to consume.
- Use prior art, go through all the official and Pavilion plugins on GitHub to see how things are done for similar actions/purposes. It’s all open source, leverage it, copy it, follow the conventions (especially those on Discourse core!)!
