MirrorMirror
/
funkwhale
mirror of https://dev.funkwhale.audio/funkwhale/funkwhale.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix some links and typo

This commit is contained in:
akhardya 2018-10-12 15:50:16 +02:00
parent 787cad6a0a
commit 6e41009be6
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CONTRIBUTING.rst
View File

@ -35,7 +35,8 @@ Setup front-end only development environment
cd funkwhale cd funkwhale
cd front cd front
2. Install [nodejs](https://nodejs.org/en/download/package-manager/) and [yarn](https://yarnpkg.com/lang/en/docs/install/#debian-stable) 2. Install `nodejs <https://nodejs.org/en/download/package-manager/>`_ and `yarn <https://yarnpkg.com/lang/en/docs/install/#debian-stable>`_
3. Install the dependencies:: 3. Install the dependencies::
yarn install yarn install
@ -47,6 +48,7 @@ Setup front-end only development environment
5. Make the front-end talk with an existing server (like https://demo.funkwhale.audio), 5. Make the front-end talk with an existing server (like https://demo.funkwhale.audio),
by clicking on the corresponding link in the footer by clicking on the corresponding link in the footer
6. Start hacking! 6. Start hacking!
Setup your development environment Setup your development environment
@ -307,7 +309,7 @@ A typical fragment looks like that:
Fixed broken audio player on Chrome 42 for ogg files (#567) Fixed broken audio player on Chrome 42 for ogg files (#567)
If the work fixes one or more issues, the issue number should be included at the If the work fixes one or more issues, the issue number should be included at the
end of the fragment (``(#567)`` is the issue number in the previous example. end of the fragment (``(#567)`` is the issue number in the previous example).
If your work is not related to a specific issue, use the merge request If your work is not related to a specific issue, use the merge request
identifier instead, like this: identifier instead, like this:
@ -507,7 +509,7 @@ useful when testing components that depend on each other:
# here, we ensure no email was sent # here, we ensure no email was sent
mocked_notify.assert_not_called() mocked_notify.assert_not_called()
Views: you can find some readable views tests in :file:`tests/users/test_views.py` Views: you can find some readable views tests in file: ``api/tests/users/test_views.py``
.. note:: .. note::