Refactor backend URL to use a centralized configuration #120
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.
Pull Request: Refactor backend URL to use a centralized configuration
Description
This pull request addresses the issue of hardcoded backend URLs in the application. The current implementation uses
localhost:3000
in multiple places, making it cumbersome to update if the backend URL changes. This update introduces a centralized configuration file to store the backend URL, ensuring that changes can be made in one location and will reflect throughout the application.Changes Made
config.js
or.env
) to store the backend URL.Updated Files and Line Numbers
Benefits
@Harshdev098
Pls add labels like hacktoberfest accepted , gssoc extd, level3 and other labels