Summary

Add a new UserDetailsProvider interface, with badge support.

Review Request #14283 — Created Jan. 2, 2025 and updated Jan. 3, 2025, 12:21 p.m.

Information

Owner

chipx86

Repository

Review Board

Branch

release-7.1.x

Bugs

Depends On

Reviewers

Groups

reviewboard

People

Description

This introduces a new concept for extensions and users, User Details

Providers, implemented as subclasses of UserDetailsProvider. This is

a class that can build upon to let exetnsions provide additional

information about users without needing to worry about extending User,

Profile, or implementing whole new hooks.
UserDetailsProvider subclasses can be registered in a central registry

and then implement methods to provide certain kinds of details that

Review Board can then query for additional functionality.
Right now, these can provide badges for users. Badges are shown

alongside a user's name in certain parts of the UI (infoboxes and

discussions, currently). They contain text and may contain custom CSS or

even custom HTML.
This is purely built for extension authors to take advantage of, giving

companies greater control over Review Board.

Testing Done

Unit tests passed.

Tested with an extension that added some hard-coded badges. Verified these
showed up in reviews, discussions, and infoboxes.

Commits

Summary	ID
Add a new UserDetailsProvider interface, with badge support. This introduces a new concept for extensions and users, User Details Providers, implemented as subclasses of `UserDetailsProvider`. This is a class that can build upon to let exetnsions provide additional information about users without needing to worry about extending `User`, `Profile`, or implementing whole new hooks. `UserDetailsProvider` subclasses can be registered in a central registry and then implement methods to provide certain kinds of details that Review Board can then query for additional functionality. Right now, these can provide badges for users. Badges are shown alongside a user's name in certain parts of the UI (infoboxes and discussions, currently). They contain text and may contain custom CSS or even custom HTML. This is purely built for extension authors to take advantage of, giving companies greater control over Review Board.	18ea34617edd8f9ba378bbbb14124f84c2aaf54a

Summary

Add a new UserDetailsProvider interface, with badge support.

This introduces a new concept for extensions and users, User Details Providers, implemented as subclasses of `UserDetailsProvider`. This is a class that can build upon to let exetnsions provide additional information about users without needing to worry about extending `User`, `Profile`, or implementing whole new hooks. `UserDetailsProvider` subclasses can be registered in a central registry and then implement methods to provide certain kinds of details that Review Board can then query for additional functionality. Right now, these can provide badges for users. Badges are shown alongside a user's name in certain parts of the UI (infoboxes and discussions, currently). They contain text and may contain custom CSS or even custom HTML. This is purely built for extension authors to take advantage of, giving companies greater control over Review Board.

18ea34617edd8f9ba378bbbb14124f84c2aaf54a

Files

Issues

Description	From	Last Updated
'io.StringIO' imported but unused Column: 1 Error code: F401	reviewbot	Jan. 2, 2025, 11:42 p.m.
'reviewboard.accounts.user_details.UserBadge' imported but unused Column: 1 Error code: F401	reviewbot	Jan. 2, 2025, 11:42 p.m.
'reviewboard.extensions.hooks.users.UserBadgeInfo' imported but unused Column: 5 Error code: F401	reviewbot	Jan. 2, 2025, 11:42 p.m.
line too long (82 > 79 characters) Column: 80 Error code: E501	reviewbot	Jan. 2, 2025, 11:42 p.m.
This looks like it's out of date/copy-pasted from elsewhere. Should say it returns a SafeString of the HTML for all …	david	Jan. 3, 2025, 12:21 p.m.
Can we move the definition of css_class down so it's right above its use?	david	Jan. 3, 2025, 12:21 p.m.

flake8 failed.

JSHint passed.

flake8

reviewboard/accounts/templatetags/accounts.py (Diff revision 1)
The issue has been resolved. Show all issues
```
'io.StringIO' imported but unused

Column: 1
Error code: F401
```
reviewboard/accounts/templatetags/accounts.py (Diff revision 1)
The issue has been resolved. Show all issues
```
'reviewboard.accounts.user_details.UserBadge' imported but unused

Column: 1
Error code: F401
```

reviewboard/accounts/templatetags/accounts.py (Diff revision 1)

The issue has been resolved. Show all issues

'reviewboard.extensions.hooks.users.UserBadgeInfo' imported but unused

Column: 5
Error code: F401

reviewboard/accounts/tests/test_template_tags.py (Diff revision 1)
The issue has been resolved. Show all issues
```
line too long (82 > 79 characters)

Column: 80
Error code: E501
```

Change Summary:


Removed unused imports.
Fixed a line length issue.

Commits:

	Summary	ID
	Add a new UserDetailsProvider interface, with badge support. This introduces a new concept for extensions and users, User Details Providers, implemented as subclasses of `UserDetailsProvider`. This is a class that can build upon to let exetnsions provide additional information about users without needing to worry about extending `User`, `Profile`, or implementing whole new hooks. `UserDetailsProvider` subclasses can be registered in a central registry and then implement methods to provide certain kinds of details that Review Board can then query for additional functionality. Right now, these can provide badges for users. Badges are shown alongside a user's name in certain parts of the UI (infoboxes and discussions, currently). They contain text and may contain custom CSS or even custom HTML. This is purely built for extension authors to take advantage of, giving companies greater control over Review Board.	70f647b787a24926709d67a021e20d6ff372c85e
	Add a new UserDetailsProvider interface, with badge support. This introduces a new concept for extensions and users, User Details Providers, implemented as subclasses of `UserDetailsProvider`. This is a class that can build upon to let exetnsions provide additional information about users without needing to worry about extending `User`, `Profile`, or implementing whole new hooks. `UserDetailsProvider` subclasses can be registered in a central registry and then implement methods to provide certain kinds of details that Review Board can then query for additional functionality. Right now, these can provide badges for users. Badges are shown alongside a user's name in certain parts of the UI (infoboxes and discussions, currently). They contain text and may contain custom CSS or even custom HTML. This is purely built for extension authors to take advantage of, giving companies greater control over Review Board.	18ea34617edd8f9ba378bbbb14124f84c2aaf54a

Diff:

Revision 2 (+1224 -26)

Show changes

	docs/manual/extending/index.rst
	docs/manual/extending/coderef/index.rst
	docs/manual/extending/extensions/hooks/index.rst
	docs/manual/extending/extensions/hooks/user-details-provider-hook.rst
	docs/stories/components/users/user-badges.stories.ts
	reviewboard/accounts/user_details.py
	reviewboard/accounts/templatetags/accounts.py
	reviewboard/accounts/tests/test_template_tags.py
	10 more

Checks run (2 succeeded)

flake8 passed.

JSHint passed.

Fix it!

reviewboard/accounts/templatetags/accounts.py (Diff revision 2)

An issue was opened. Show all issues

This looks like it's out of date/copy-pasted from elsewhere. Should say it returns a SafeString of the HTML for all badges.

reviewboard/accounts/user_details.py (Diff revision 2)

An issue was opened. Show all issues

Can we move the definition of css_class down so it's right above its use?