Mazevo api key fix - #182
Open
justinschwerdtfeger wants to merge 7 commits into
Open
Conversation
… API. Mazevo API Key no longer needed
Contributor
|
Cool stuff! Will review this weekend |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #179
Due to Mazevo API requiring the X-Signature header, recreating Mazevo's api requests is challenging.
Instead, this new PR uses ChromeDP to directly navigate to Mazevo's Calendar
Recreating the API requests that this page uses from scratch ideal, and if someone can find out how X-Signature is calculated, that should be possible as far as I understand.
For now, this approach should work for Nebula-API's needs, and only takes a few seconds to scrape.
With this, the Mazevo API Key is no longer required for scraping, and is removed from .env.template