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
💡 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! 👋
Current Behavior
Error when accessing the forum after saving in the admin panel a custom CSS code of +68000 characters (doesn't mean it's exactly that number, in my case I've experienced it when reaching that number of characters).
This causes that when saving the CSS code the last lines are cut, and therefore in my case for example this caused a `ParseError: missing closi
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).
What needs to be done?
Curate a list of terms to avoid and appropriate alternatives (Is there a catalogue already in existence we can link to?)
Currently, links in the above-described components are rendered as texts, hence users can't click on them.
I propose creating a utility function that identifies links in text and wraps them in an Anchor tag, with the following properties: target="__blank" rel="noreferrer noopener" and use that function for rendering texts in the relevant components.
Describe the bug
As an administrator when setting up categories, I have a "description" field. This isn't used for anything and it's confusing to have it, specially as it's a required field.
To Reproduce
Steps to reproduce the behavior:
Sign in as admin
Go to Admin Dashboard (/admin) -> Processes -> Select a Process -> a Process -> Categories -> New category
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