Hello @nayakastha , That's a great improvement to the code. Have a pinch of paitence while the reviewer gets impressed by the changes you made. Here are some doggos for company while you are waiting for the merge and marching ahead with your Hacktoberfest Contributions, Check your Dashboard for more information on Hacktoberfest. Stay safe 🚀 .

Hello @nayakastha , That's a great improvement to the code. Have a pinch of paitence while the reviewer gets impressed by the changes you made. Here are some doggos for company while you are waiting for the merge and marching ahead with your Hacktoberfest Contributions, Check your Dashboard for more information on Hacktoberfest. Stay safe 🚀 .

Hello @nayakastha , That's a great improvement to the code. Have a pinch of paitence while the reviewer gets impressed by the changes you made. Here are some doggos for company while you are waiting for the merge and marching ahead with your Hacktoberfest Contributions, Check your Dashboard for more information on Hacktoberfest. Stay safe 🚀 .

@nayakastha
It is better if you always write description for the PR

I see that there are a lot of file renames and many other such changes that are irrelevant to the PR. Why did that happen?

The WOC Codes are repeated codes and have not been implemented yet. So them being stored along with the initial files created a tad bit of confusion. So arranged it within the correct folder for Stacked Architecture

I would suggest to update the PR title as it is not just Remote Config but much more than that

@DesignrKnight review this PR if possible.