-
Notifications
You must be signed in to change notification settings - Fork 2.7k
GH-7680 Migrate get post link modal to be pure #234
GH-7680 Migrate get post link modal to be pure #234
Conversation
Hi, this is my first try to work on the webapp, let me know if there is any problem. |
Great, thanks @h2oloopan! Looks like the build fails, can you take a look at it? If you're not sure why, let us know and we can help out |
Hmm, I can't check details on GitHub. I will see if the build problem occurs on my local machine when I get home. On the other hand, can you help me post the error log from the build server here so I can take a look at it first? Thanks! |
Looks like the build suddenly stopped halfway through for no reason. Re-running it |
You've got this style error:
|
…migrate-get-post-link-modal
Was travelling on the weekend. Finally got back home and setup eslint on my local machine. The semicolons should have been fixed now. |
@h2oloopan Thank you for your contribution! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
@saturninoabril Thanks for the added test! |
Thanks for this @h2oloopan ! |
* only set fetch's credentials:include option if no access token this is what client.js does, and fixes a CORS issue when running client4.js in a browser. Specifically, the issue seen is: Fetch API cannot load http://127.0.0.1:8065/api/v4/users/me. Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Credentials' header in the response is '' which must be 'true' when the request's credentials mode is 'include'. Origin 'http://127.0.0.1:8002' is therefore not allowed access. * Revert "only set fetch's credentials:include option if no access token" This reverts commit 2ba1306a69e46f84a7143c2ce2753a1f222cb118. * make sending credentials via fetch configurable in client4.js this preserves the default behaviour of sending cookies as part of the request, but can be turned off with client.setIncludeCookes(false).
* only set fetch's credentials:include option if no access token this is what client.js does, and fixes a CORS issue when running client4.js in a browser. Specifically, the issue seen is: Fetch API cannot load http://127.0.0.1:8065/api/v4/users/me. Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Credentials' header in the response is '' which must be 'true' when the request's credentials mode is 'include'. Origin 'http://127.0.0.1:8002' is therefore not allowed access. * Revert "only set fetch's credentials:include option if no access token" This reverts commit 2ba1306a69e46f84a7143c2ce2753a1f222cb118. * make sending credentials via fetch configurable in client4.js this preserves the default behaviour of sending cookies as part of the request, but can be turned off with client.setIncludeCookes(false).
Summary
Migrated get post link modal to be a pure component and use Redux.
No store or action is involved
Ticket Link
mattermost/mattermost#7680
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]