Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API Context for User-Reported Data #88

Closed
wants to merge 4 commits into from

Conversation

evanjscallan
Copy link
Contributor

Proposed is an implementation of a context element where live data can be implemented into components.
This element utilizes our back-end GQL server where user-reported data is logged. Currently the code is set up to process date-related data but other queries can be added as well.

As of now, no existing UI elements are affected by this addition. The addition is simply a functionality update.
For information on how the data pull works (with an example), please refer to issue #84.

Notes:
-The addition is currently a hybridized version of tsx with several 'normal' js/jsx elements still in place.
-Future plans are to convert this component into a functional one rather than a class component with full typescript conversion.

This may also be implemented as a render prop or higher-order component. Let me know if you have any thoughts/queries/ideas/etc.

@netlify
Copy link

netlify bot commented Apr 25, 2022

Deploy Preview for orcahome failed.

Name Link
🔨 Latest commit 9b4df36
🔍 Latest deploy log https://app.netlify.com/sites/orcahome/deploys/62e2ebc5fbeea500094dd1b3

@evanjscallan
Copy link
Contributor Author

Will circle back around on PR once stylistic rules are satisfied.

@rodrickcalvin
Copy link
Contributor

@evanjscallan can we link up and solve the issue

@evanjscallan
Copy link
Contributor Author

evanjscallan commented Oct 11, 2022 via email

@netlify
Copy link

netlify bot commented Mar 12, 2023

Deploy Preview for orcahome failed.

Name Link
🔨 Latest commit 5813b3c
🔍 Latest deploy log https://app.netlify.com/sites/orcahome/deploys/640e3456fa90410008814302

@evanjscallan
Copy link
Contributor Author

Problem should be fixed with refactoring and UTC update. Will open a new PR shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants