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
The skeleton for the events index is already built on the feature/events branch.
Next steps (will accept a Techlahoma Hacktoberfest PR for each item)
install graphql-request as a dependency
configure graphql client for meetup api (only need to be able to fetch data for techlahoma events and filter to code for tulsa)
In the getStaticProps() call on the Event index client:
Fetch the data and format it as needed based on event cards
merge it with the other event data coming from github (this functionality not implemented yet, see Feat: Event Calendar #53
replace the hard-coded sample data with the live data
The text was updated successfully, but these errors were encountered:
For the events page, we'd like to query the Meetup API for Techlahoma events and filter down to Code for Tulsa events and possibly other Tulsa org events. We might also want to look at CfA events, tbd.
zenlex
changed the title
Install Apollo client and configure to pull Meetup data
Install graphql client and configure to pull Meetup data
Aug 24, 2022
We're only issuing GraphQL queries in a limited set of circumstances, so a fully-featured GraphQL client might be overkill. Here are some ideas for a minimalist approach:
The skeleton for the events index is already built on the
feature/events
branch.Next steps (will accept a Techlahoma Hacktoberfest PR for each item)
graphql-request
as a dependencyIn the getStaticProps() call on the Event index client:
The text was updated successfully, but these errors were encountered: