Граф коммитов

9 Коммитов

Автор SHA1 Сообщение Дата
Eemeli Aro 5a2b145170
Drop remnants of in-context localization (#2862)
* Drop pontoon/in-context/

* Drop subpages

* Drop project links, url & width fields

* Drop pontoon.js

* Drop remaining mentions of in-context localization
2023-06-15 13:59:23 +03:00
Willian Gustavo Veiga 01cddfd0df
Upgrade jQuery to v3.6.1 (#2647)
* Upgrade jQuery
* Upgrade jQuery UI
* Use original jQuery files instead of minified ones
* Remove unusued jQuery UI CSS file
* Remove unused jQuery UI from admin
* Move $.ajax callbacks to parameters
2022-11-25 10:37:20 +01:00
Matjaž Horvat 5542b6b428
Run Prettier and ESLint in relevant folders only (#2597)
* Prettier: Ignore static, media and .github folders

* ESLint: Ignore static, media and .github folders
2022-08-09 17:10:05 +02:00
Eemeli Aro 9faea69c20
Set `tabWidth: 2` in Prettier config (#2438)
* chore: Update Prettier config, setting tabWidth:2

* style: Apply updated Prettier styles

If you need to rebase work past this style change, do as follows:

0. Consider this to be commit `commitA`, replacing that with its id in the following.
1. To make sure mistakes aren't fatal, assign a second branch to your current work.
2. Rebase your branch on the commit immediately before this one, commitA~
3. Run the following command at the root of the repo:

    git rebase --strategy-option=theirs \
      --exec 'npx prettier --write . && git add -u && git commit --amend --no-edit' \
      commitA

That will take a short while esp. if you have multiple commits,
as it runs Prettier on everything for every commit.
If you've deleted files, the rebase may drop down to interactive mode
and have you `git rm` as appropriate, then `git rebase --continue`.

You should end up with just your changes in your branch,
prettily formatted. To validate that,
apply the same Prettier config change to your original branch,
reformat the files with `npm run prettier`,
and then compare the results with the rebased branch.

* chore: Clean up lint configs
2022-03-03 09:46:35 +01:00
Eemeli Aro d26c91487e
Handle the `tags/admin/` client as an npm workspace at `/tag-admin/` (#2430)
* Move tag-admin sources & tests to /tag-admin/src/

Import paths are modified to use relative, fully qualified file names.

* Configure tag-admin as an npm workspace

* Fix build & CI issues

Consistently call 'npm ci' and 'npm run build' where appropriate

* Apply lint & style rules to tag-admin/webpack.config.js

* Fix permissions for /tag-admin/ in Dockerfile

* ci: Rename "non-frontend-js" action as "tag-admin"

* docs(tag-admin): Add README
2022-02-16 16:47:32 +02:00
Adrian Gaudebert 43becde477
Fix bug 1473330 - Translate.Next architecture (#989)
* Add React frontend for Translate app.
This has been set up using create-react-app.

* Integrate new Translate app into django.
This provides a working prod and dev environment. In production, django will serve the index.html file as a template, and files built by webpack will be collected and distributed with other django static files. In development, all requests are proxied to the dev webpack server, allowing all dev niceties to be used.

* Add support for websockets.

* Add a bit of documentation specific to our use case.

* Add redux for state management.

* Show a very basic list of entities.

* Enable absolute path import.

* Add links to various resources.

* Rearchitecture code into modules.

All features should be self-contained into a module in src/modules/. All code that is shared amongst several modules should go into a module in src/core/.

* Remove unused assets.

* Add some architecture documentation.

* Add Flow to current code for type checking.

* Add unit testing with jest, enzyme and sinon.

* Extend documentation, talk about type checking, modules, and list tools we use.

* Move CSS rules closer to actual component.

* Add django-waffle and hide translate.next behind a switch.

* Better structure for the README file.

* Build and test frontend in travis.

* Of course it is better if dependencies are installed.

* Use pushd to run commands in frontend.

* Configure eslint and fix errors.

* Add more code comments.

* Improve documentation around local dev and Flow.

* Add tests for the Translate view.

* Improve documentation.

* Fix serving static files for development.

* Integrate Translate.Next with out docker setup.

* Remove debug.

* Use DEV instead of DEBUG.

* Much review.
          Many comments.
    Wow better!

* Flatter module public interfaces.

* Import correctly from modules.

* Fix docker webapp run.
2018-07-18 11:39:52 +02:00
Ryan Northey fb320dbecd Touch Bug 1437273: Eslint fixes 2 #858
- Add js template to eslintignore
- Fix eslint errors in translate.js
- Make travis fail for eslint errors
2018-02-13 19:44:10 +00:00
Ryan Northey 30cb4c1a60 Touch Bug 1243129: linting, react env and a widget #818
- Update travis linting
  - Make travis eslint fail for pontoon/static and tests/js
  - Add pylama for tests dir
- Update eslint to handle ecma 2017
- Add a checkbox widget with indeterminate functionality
- Remove placeholder test
- Fix pylama and eslint errors in tests and pontoon/static
- Add test for checkbox widget
- Add assets folder to eslintignore
2018-01-25 11:53:10 +00:00
Ryan Northey 6ac3152213 Touch Bug 1243129: Js testing and linting #804
- Add test dependencies for react testing and set up jest
- Add placeholder js test
- Add jest to travis run
- Add eslintrc
- Add eslintignore
2018-01-18 16:04:40 +00:00