Skip to content

Small language improvements and typo fix #3226

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 27, 2025
Merged

Small language improvements and typo fix #3226

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions doc/manual/develop.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,24 +187,24 @@ Loading development fixture data
To debug failing Unit tests the fixtures can be loaded with:
``./webapp/bin/console domjudge:load-development-data SampleSubmissionsFixture`` in the current database.

Installing, uppdating & upgrading dependencies
-----------------------------------
To manage the PHP dependencies start from ``/webapp``.
Installing, updating & upgrading dependencies
---------------------------------------------
To manage the PHP dependencies, use the commands below from the ``webapp`` directory.

To require a new dependency/library:
``composer require package/name`` or ``composer require package/name:version``, this is most often needed
when a newer version is broken, is needed because you need a specific new feature or when you need a new library.
when a newer version is broken, or when you need a specific new feature or new library.

To update all dependencies:
``composer update``, this is useful before a new contest when there is enough time to fix possible issues.

To update a single dependency:
``composer update package/name`` and ``composer update -W package/name`` for either a single package upgrade or
also the other requirements if needed. For the second case ``composer`` is allowed to update a dependency in case the
also the other requirements if needed. In the second case, ``composer`` is allowed to update a dependency in case the
dependency ``package/name`` requires a higher version.

When you expect a dependency to upgrade and it doesn't you can check on `Packagist`_ if a newer version exists
and change the version in `composer.json`, or use `composer require package/name:version`` and rerun the commands above.
When you expect a dependency to upgrade and it doesn't, you can check on `Packagist`_ if a newer version exists
and change the version in `composer.json`, or use ``composer require package/name:version`` and rerun the commands above.

.. _CCS Contest API specification: https://ccs-specs.icpc.io/2021-11/contest_api
.. _OpenAPI Specification ver. 3: https://swagger.io/specification/
Expand Down
Loading