Closed bnjmnt4n closed 3 years ago
Note: this commit causes both SearchInGhost and our custom event loading code to use the same content API key. I don't think there's much disadvantage to that, but we can always switch back to using separate keys if desired.
LGTM, I think it makes more sense to stick to a single standard Content API key. Thanks for the PR!
Note: this commit causes both SearchInGhost and our custom event loading code to use the same content API key. I don't think there's much disadvantage to that, but we can always switch back to using separate keys if desired.