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
{{ message }}
This repository was archived by the owner on Dec 3, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 3, 2019. It is now read-only.
Mentor Requests Are Not Populating to Airtable #155
Submitting the Mentor Request form from front-end at https://operationcode.org/mentor-request doesn't populate the Airtable with the request via the back-end API.
re: 'is there a current process for the airtable request form linking back to our current site? if yes, what is it?' - Not that I'm aware of. Sounds like the integration w/ the Airtable API might have not been built in as a feature while the new site was set up? I'm not very familiar with Rails anymore, but I scanned through the API requests_controller.rb and the rest of the back-end and didn't see any Airtable-related stuff.
re: 'should this be converted to a feature request for the backend to expose a new endpoint that populates Airtable with the passed mentor request?' - Seems like a new feature request could work,
but we might just want to bypass the idea of populating Airtable, since we've talking about moving mentor service requests to populate on Discourse? (issues / milestones have not been created for that idea yet). Might be a better use of resources for our back-end team as we try to phase out Airtable. @rickr might be able to weigh in on this.
Short term fix, if we merge in front-end PR 466, we can just link directly from our page to the Airtable form to let users populate Mentor Service Requests. Then we can revise our in-app form and back-end API to integrate (with either Airtable, Discourse, or anything else).
@jjhampton - Thanks. I actually removed my comment. Reason being, I mistakenly relied on GitHub's search feature, from an iPad. It returned no results for anything airtable related.
But after searching in sublime, it turns out there is a background job in the backend repo that pings airtable's API. It is triggered by an after_create callback on User.
I haven't dug in any further, but at first blush this does appear to be a bug, as you reported.
Closing this issue as it was originally thought there was a bug preventing the API call to Airtable. When in fact, this functionality does not currently exist, and would/could be a future feature request.
Activity
jjhampton commentedon Sep 4, 2017
Thanks for looking into this, @hpjaj .
re: 'is there a current process for the airtable request form linking back to our current site? if yes, what is it?' - Not that I'm aware of. Sounds like the integration w/ the Airtable API might have not been built in as a feature while the new site was set up? I'm not very familiar with Rails anymore, but I scanned through the API
requests_controller.rband the rest of the back-end and didn't see any Airtable-related stuff.re: 'should this be converted to a feature request for the backend to expose a new endpoint that populates Airtable with the passed mentor request?' - Seems like a new feature request could work,
but we might just want to bypass the idea of populating Airtable, since we've talking about moving mentor service requests to populate on Discourse? (issues / milestones have not been created for that idea yet). Might be a better use of resources for our back-end team as we try to phase out Airtable. @rickr might be able to weigh in on this.
Short term fix, if we merge in front-end PR 466, we can just link directly from our page to the Airtable form to let users populate Mentor Service Requests. Then we can revise our in-app form and back-end API to integrate (with either Airtable, Discourse, or anything else).
hpjaj commentedon Sep 4, 2017
@jjhampton - Thanks. I actually removed my comment. Reason being, I mistakenly relied on GitHub's search feature, from an iPad. It returned no results for anything airtable related.
But after searching in sublime, it turns out there is a background job in the backend repo that pings airtable's API. It is triggered by an
after_createcallback onUser.I haven't dug in any further, but at first blush this does appear to be a bug, as you reported.
hpjaj commentedon Sep 4, 2017
@jjhampton - as you uncovered in Slack, the
AddUserToAirtablesJobbackground job creates a user in Airtable, not a mentor request.We would need a new feature request for that, or one for moving to Discourse as you described above.
hollomancer commentedon Sep 5, 2017
@jjhampton @rickr, do we want to make the web interface for mentors invisible for now, and just go straight to Discourse implementation?
hpjaj commentedon Oct 8, 2017
Closing this issue as it was originally thought there was a bug preventing the API call to Airtable. When in fact, this functionality does not currently exist, and would/could be a future feature request.