In many (if not all!) of the places where the Follow button is rendered (with the class follow-action-button), the button always renders the text Follow by default. Once the user's data is fetched, it then may update to Following. This step of fetching the data async and then updating the text after the button and text have already rendered leads to a glitchy UI
When running ./nodebb upgrade, the output should also append to logs/output.log just as it does for ./nodebb start. These logs can be viewed by running ./nodebb log.
Good for beginners, feel free to ask here for tips on getting started.
💡 Looking for inspiration for your next open source project? Or perhaps you've got a brilliant idea you can't wait to share with others? Open Source Ideas is a community built specifically for this! 👋
Currently, there's a lot of duplication between the tags Tag content handler and core's Index content handler. Similar duplication exists in "index" blade template vs "tag" bla
Now that our default branch is called main we should do a search for other such terms (e.g. blacklist and whitelist) and update them with more modern alternatives, (e.g. denylist and allowlist).
Describe the bug
When using hidden param in moderation the filters strips out the hidden param. The consequence is that you cannot search or filter by hidden: true
To Reproduce
Steps to reproduce the behavior:
Go to /admin/participatory_processes/YOUR_PROCESS/moderations
Describe the bug
In many (if not all!) of the places where the
Followbutton is rendered (with the classfollow-action-button), the button always renders the textFollowby default. Once the user's data is fetched, it then may update toFollowing. This step of fetching the data async and then updating the text after the button and text have already rendered leads to a glitchy UI