New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v3.6.5 #1261
Release v3.6.5 #1261
Commits on Apr 24, 2019
-
LBSD-2326 Add WhatsApp, Telegram and Viber to the SHARE button
Removed G+ sharing option from AMP and Default theme Fixed some warning on AMP theme and also improved comment form
Commits on Apr 25, 2019
Commits on Apr 29, 2019
Commits on Apr 30, 2019
Commits on May 3, 2019
Commits on May 9, 2019
Commits on May 10, 2019
-
LBSD-2379 Completed migration of flux module to TS and turned it into…
… proper es6 class Added types for this module, first ones in Liveblog
-
-
Commits on May 14, 2019
Commits on May 16, 2019
Commits on May 21, 2019
-
LBSD-2393 Adding ability to listen to editor changes in debounced mode
Then we hit the backend to update the flag of post so this way we have a real sense of activity in the editor. This will make a better TTL for the flag, as it will count the expiration the last time user modified something in the editor
-
Commits on May 24, 2019
-
LBSD-2393 Implements new modal dialog for posts being edit which edit…
… flag expire With this new approach we are trying to solve the problem of auto-closing the editor when the edit flag TTL reached so instead we now have our own modal building components and a custom modal dialog that allows the user picking from three options instead of closing the editor. Additionally, the components were build using React and Typescript which makes them the first ones in our stack :) the components are mostly react and they have a small combination with angular logic.
Commits on May 28, 2019
-
I have tried so many things on this topic. I'm listing some of them: - Putting the webdriver-update and protractor commands directly in travis.yml file - no difference as using the npm run alternative makes them run correctly after all - Update chrome driver to match current version of Chrome (v74 at the moment) - Fixed CELERY_BEAT settings as this was adding lot of noise in the logs - Found and fixed broken test connected with new modal window introduced in this release - we need to invest some time to improve some logic in the tests, like avoid using too open selectors
-