You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some brigades may have their site organized with a dedicated page for each project. It would be much more useful to have a filter option, similar to labels, that would allow them to specify which repositories they would like to include in their embed. Allowing multiple repositories would still allow for projects spread out accross multiple repos (infrastructure, backend, frontend, mobile app) to could still allow for one embed dedicated to a single project.
The text was updated successfully, but these errors were encountered:
On /geeks/civicissues/embed when you select an organization, it should bring you to the page /geeks/civicissues/embed/<organization> using js/main.js.
In app.py add a new route /geeks/civicissues/embed/<organization>. This route will make a request to http://codeforamerica.org/api/organizations/<organization>/projects and hand off all the projects to the embed template.
If the embed template receives projects, then show a select multiple form element listing all the projects alphabetically. templates/embed.html
Each project selected should update the embed iframe code with a &projects= parameter. Use js/main.js
The /geeks/civicissues/widget route in app.py should accept the projects parameter and use to add &project_name=project 1, project 2, project 3 to the CfAPI request.
The Issues endpoint in the CfAPI will need to be updated to take in the project names and do an OR query against each of them to get all matching issues.
Some brigades may have their site organized with a dedicated page for each project. It would be much more useful to have a filter option, similar to labels, that would allow them to specify which repositories they would like to include in their embed. Allowing multiple repositories would still allow for projects spread out accross multiple repos (infrastructure, backend, frontend, mobile app) to could still allow for one embed dedicated to a single project.
The text was updated successfully, but these errors were encountered: