Repository navigation
Fix normalizePort and consolidate delete handlers - #136
Merged
Merged
Conversation
…nicating with RERUM API
…nicating with RERUM API
thehabes
self-requested a review
October 26, 2026 16:32
thehabes
approved these changes
Oct 26, 2026
thehabes
left a comment
Member
There was a problem hiding this comment.
Changes tested and successful. TinyNode itself will always call to RERUM using the "/delete/{_id}" pattern.
This branch was successfully deployed
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.
This PR addresses two related issues:
tinyNode.js normalizePort() is not doing okay #52
tinyNode.js normalizePort() is not doing okaynormalizePort()call:const port = normalizePort(process.env.PORT) || 3002normalizePort()to validate that the value is an integer between 1 and 65535, returningfalseotherwise so.listen()always receives a number.Remove double DELETE handling #64 Remove double DELETE handling
router.delete()handlers inroutes/delete.jsinto a singledeleteRecordhandler that extracts the@idfrom either the path parameter or the request body and performs the delete.Fixes #52
Fixes #64