Repository navigation
fix(compatibility): a renamed function's old route is not a known issue - #6
Merged
Merged
Conversation
The compatibility page listed, as 0.2.4's one known issue, that a function
removed, renamed or moved to another region keeps its old route until a
restart. The official emulator does the same: after a rename, firebase-tools
15.35.0 answers the old route `500 {"code":"ECONNRESET"}`, as Firenook does.
The entry goes, the Functions page says the official emulator behaves the
same, and the page leaves out the known issues section, and the link to it,
while there are none.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01APfZAFCQzCmvhJqWKMT47g
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
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.
The compatibility page listed, as 0.2.4's one known issue, that a function removed, renamed or moved to another region keeps its old route until a restart. The official emulator does the same. Checked today on one project: after a rename, firebase-tools 15.35.0 and Firenook 0.2.4 both answer the old route
500 {"code":"ECONNRESET"}, and both serve the new name.Checked:
npm run check, the build andnpm run check:site.🤖 Generated with Claude Code
https://claude.ai/code/session_01APfZAFCQzCmvhJqWKMT47g