Connector per Mobilizon ti permette di visualizzare i prossimi eventi di Mobilizon sul tuo sito WordPress.
https://mobilizon.it
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
1 month ago | |
---|---|---|
.github/workflows | 4 months ago | |
.husky | 2 years ago | |
assets | 12 months ago | |
source | 1 month ago | |
.eslintrc.json | 1 year ago | |
.gitignore | 2 years ago | |
.gulp.json | 1 year ago | |
.prettierignore | 2 years ago | |
.prettierrc.json | 2 years ago | |
LICENSE.md | 2 years ago | |
README.md | 12 months ago | |
babel.config.json | 2 years ago | |
composer.json | 2 years ago | |
composer.lock | 2 years ago | |
gulpfile.cjs | 1 year ago | |
icon.afdesign | 2 years ago | |
package-lock.json | 1 month ago | |
package.json | 1 month ago | |
qodana.yaml | 2 months ago | |
webpack.config.cjs | 1 year ago |
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
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