fix: align collection bani IDs with GurbaniNow API #320
Conversation
This file contains 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
Harjot1Singh
force-pushed
the
migrate-to-expo
branch
27 times, most recently
from
81e60fc to
f0b34e0
Compare
Harjot1Singh
force-pushed
the
migrate-to-expo
branch
27 times, most recently
from
d5549df to
0169fc3
Compare
|
Fixed in main |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The collection Bani IDs are currently aligned with gurbaninow.com/gutka. Unfortunately, these IDs are currently sourced from a slightly different GN API, which does not have the same IDs as api.gurbaninow.com, which we're currently using