Skip to content

MDL-77353 Functions for generating and displaying user details #634

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tuanngocnguyen wants to merge 1 commit into from
Closed

MDL-77353 Functions for generating and displaying user details #634

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/devupdate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,3 +9,9 @@ tags:
import { CodeBlock, CodeExample, InvalidExample, ValidExample } from '@site/src/components';

This page highlights the important changes that are coming in Moodle 4.3 for developers.

## Functions for generating and displaying user details
Copy link
Collaborator

@junpataleta junpataleta May 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A more appropriate heading would be something like "User-related API updates", then followed by a paragraph that describes the update. e.g. "New functions for generating and displaying user details have been created:", then followed by the list of the new user functions.


#### `core_user::get_profile_picture` for retrieving user picture.
Copy link
Collaborator

@junpataleta junpataleta May 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use lists for the methods instead of headings.

Also, something to remember for the future: For accessibility reasons, headings must increase by one level. e.g. an h2 heading needs to have an h3 heading underneath it.

#### `core_user::get_profile_url` for retrieving profile url.
#### `core_user::get_fullname` for retrieving user full name.