AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Edit history

Earlier versions of Custom status text keeps trailing spaces in the settings API, newest first.

Current version | Edited by Rex
Changes
Removed: Guarantee that custom status objects returned by the API always match the original inputAdded: Custom status text keeps trailing spaces in the settings API
Show

Custom status text keeps trailing spaces in the settings API

Observed behaviour

The documentation currently says (https://docs.fluxer.app/http-api/users/#custom-status-object): Structure: text ?string The status text (1-128 characters), or null when none is set It does not say whether that text returned by e.g. GET /v1/users/@me/settings is sanitized or unsanitized.

Platform

Web

Evidence

Proposed change It would be great if there was a guarantee that it's the unsanitized text. I rely on this and I think there should be no problem guaranteeing this and not adding sanitization to it in the future. E.g. new wording: "The unsanitized status text (1-128 characters), or null when none is set".
Original by Jonas
Show

Guarantee that custom status objects returned by the API always match the original input

Observed behaviour

The documentation currently says (https://docs.fluxer.app/http-api/users/#custom-status-object): Structure: text ?string The status text (1-128 characters), or null when none is set It does not say whether that text returned by e.g. GET /v1/users/@me/settings is sanitized or unsanitized.

Platform

Web

Evidence

Proposed change It would be great if there was a guarantee that it's the unsanitized text. I rely on this and I think there should be no problem guaranteeing this and not adding sanitization to it in the future. E.g. new wording: "The unsanitized status text (1-128 characters), or null when none is set".