There Will Always be a Bumpy Road

Bthari here, and I want to tell you that... I got a problem, we all do actually.
First, there's the CORS as my friend Glory already writes in her post here. We can generate the front-end view, because there's an error in response like, "No 'Access-Control-Allow-Origin' header is present on the requested resource." But when you type the URL in a browser, "/API/v1/<api-name>" it shows something actually. Well, turns out we just need a little change in our backend and frontend service, add CORS when we want to access an API setting response.headers.add('Access-Control-Allow-Origin', '*')
Then, the git flow after we pushed to sit_uat, and we need to fix in coldfix, yet we have something left in the user_story branch! Thanks to my friend Rafiano (one of the masters—the other on is Wisnu—of the convention name for git-branch and control for git-flow), he keeps me on the right track. We work on the branch user_story (additionally, our team have branch task, which means we need to merge it first to user_story), then merge branch user_story into sit_uat; if there's an error or a need to refactored there, fix it on coldfix; if coldfix is used, but there's a change in sit_uat, pull sit_uat first into coldfix; last, when thing are right, merge coldfix to sit_uat. Oh, don't forget to create merge from merge request ;)
Wish us, we can survive all the storm :)

0 komentar:

Post a Comment