56a59e1b55
Things like `speed=0.1s` now work I also noticed a class was set on StatusBody, but we don't use it, we use StatusContent. Therefor I removed it now. We do still pass the setting through StatusBody to RichContent bc it's used there to decide to not show greentext for arrows when MFM was used. Note that while this setting still works * You have to refresh the page to see it working (was already like this, so I didn't touch it here) * It explicitly checks for content type. If womeone provides MFM-like HTML, then it will still show as greentext if that option is enabled I think it's a bit inconsistent, but otoh, the inconsistency to me seems more that we ignore the greentext option for one input type specifically I do still notice generall bugs with MFM. * Position doesn't seem to work, neither does scale. * There also seems to be a regression where custom emojis don't become larger any more with e.g. `$[x2 :hehe: ]` I don't assume the regression is made in this commit, so I add this already. The rest needs to be fixed before merging. |
||
|---|---|---|
| .gitea/issue_template | ||
| build | ||
| config | ||
| docs | ||
| src | ||
| static | ||
| test | ||
| tools | ||
| .babelrc | ||
| .editorconfig | ||
| .gitignore | ||
| .mailmap | ||
| .node-version | ||
| .stylelintrc.json | ||
| .tool-versions | ||
| .woodpecker.yml | ||
| BREAKING_CHANGES.md | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTORS.md | ||
| eslint.config.js | ||
| index.html | ||
| LICENSE | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| renovate.json | ||
| yarn.lock | ||
Akkoma-FE
This is a fork of Akkoma-FE from the Pleroma project, with support for new Akkoma features such as:
- MFM support via marked-mfm
- Custom emoji reactions
For Translators
The Weblate UI is recommended for adding or modifying translations for Akkoma-FE.
Alternatively, edit/create src/i18n/$LANGUAGE_CODE.json (where $LANGUAGE_CODE is the ISO 639-1 code for your language), then add your language to src/i18n/messages.js if it doesn't already exist there.
Akkoma-FE will set your language by your browser locale, but you can temporarily force it in the code by changing the locale in main.js.
FOR ADMINS
To use Akkoma-FE in Akkoma, use the frontend CLI task to install Akkoma-FE, then modify your configuration as described in the Frontend Management doc.
Build Setup
# install dependencies
corepack enable
yarn
# serve with hot reload at localhost:8080
npm run dev
# build for production with minification
npm run build
# run unit tests
npm run unit
For Contributors:
You can create file /config/local.json (see example) to enable some convenience dev options:
target: makes local dev server redirect to some existing instance's BE instead of local BE, useful for testing things in near-production environment and searching for real-life use-cases.staticConfigPreference: makes FE's/static/config.jsontake preference of BE-served/api/statusnet/config.json. Only works in dev mode.
FE Build process also leaves current commit hash in global variable ___pleromafe_commit_hash so that you can easily see which pleroma-fe commit instance is running, also helps pinpointing which commit was used when FE was bundled into BE.
Configuration
Edit config.json for configuration.
Options
Login methods
loginMethod can be set to either password (the default) or token, which will use the full oauth redirection flow, which is useful for SSO situations.