The B64Url is currently not exposed this makes it hard to implement any From/To for it, one use case we have is that since IDs are required on EditableFields we would like to generate these on the fly.
â° Reminders before review
Contributor guidelines followed
All formatters and local linters executed and passed
Written new unit and / or integration tests where applicable
Protected functional changes with optionality (feature flags)
Used internationalization (i18n) for all UI strings
CI builds passed
Communicated to DevOps any deployment requirements
Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team
đĻŽ Reviewer guidelines
đ (:+1:) or similar for great changes
đ (:memo:) or âšī¸ (:information_source:) for notes or general info
â (:question:) for questions
đ¤ (:thinking:) or đ (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
đ¨ (:art:) for suggestions / improvements
â (:x:) or â ī¸ (:warning:) for more significant problems or concerns needing attention
đą (:seedling:) or âģī¸ (:recycle:) for future improvements or indications of technical debt
đ Objective
The B64Url is currently not exposed this makes it hard to implement any From/To for it, one use case we have is that since IDs are required on
EditableField
s we would like to generate these on the fly.â° Reminders before review
đĻŽ Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or âšī¸ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or đ (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or â ī¸ (:warning:
) for more significant problems or concerns needing attention:seedling:
) or âģī¸ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes