Connector per Mobilizon ti permette di visualizzare i prossimi eventi di Mobilizon sul tuo sito WordPress.
https://mobilizon.it
dc1949ba4c | ||
---|---|---|
.github/workflows | ||
.husky | ||
assets | ||
source | ||
tests | ||
.eslintrc.json | ||
.gitignore | ||
.gulp.json | ||
.prettierignore | ||
.prettierrc.json | ||
LICENSE.md | ||
README.md | ||
babel.config.json | ||
composer.json | ||
composer.lock | ||
gulpfile.cjs | ||
icon.afdesign | ||
package-lock.json | ||
package.json | ||
phpunit.xml | ||
qodana.yaml | ||
webpack.config.cjs |
README.md
Connector for Mobilizon
Connector for Mobilizon allows you to display the upcoming events of Mobilizon, which is a federated event listing platform, on your WordPress website.
More details can be found in the WordPress Plugin Directory.
The current changelog can be found under source/changelog.txt.
Development
Setup
- Make sure
npm
andcomposer
are installed. - Run:
npm install
- Run:
composer install
Development build
- Build:
npm run build-dev
- Make sure to keep
changelog.txt
up-to-date.
Release procedure
- Make sure
changelog.txt
is up-to-date. - Use a new version number and copy over the new section into
readme.txt
. - Update
package.json
with the same version number. - Update the
package-lock.json
:npm i --package-lock-only
- Build:
npm run build-prod
- Make sure screenshots are up-to-date.
- Copy the built plugin into
/trunk
of SVN. - Create a new tag of the new version:
svn cp trunk tags/<version>
- Check the version number occurrences in both folders.
- Commit everything together to the release SVN:
svn ci -m "release version <version>"
Make sure to add new files beforehand. - Commit the new version in git with the same message.
- Tag the new version:
git tag v<version>
- Push the new tag to the repository:
git push --tags
- Append
-next
to the version number inpackage.json
. - Update the
package-lock.json
:npm i --package-lock-only
- Commit:
git commit -am "prepare next release"
Other commands
- Run ESLint:
npm run eslint
- Run JavaScript code coverage with tests:
npm run coverage
- Run tests:
npm test
- Delete build folder:
npm run clean
- Update PHP dependencies:
composer update
- Check for direct PHP dependency updates:
composer outdated --direct
- Format code with prettier:
npm run format
- Generate
vendor/autoload.php
file after creating new class:composer dump-autoload