Problem/Motivation

Drupal core marked its float fields as "no_ui" because of the inherent problems of floating point maths and there being really no value from a site builder's perspective to use floats over decimals. See #2542760: Mark float and list (float) field types as no_ui and the associated change record for more information.

The range module provides a "Range (float)" field type.

Steps to reproduce

-

Proposed resolution

Let's follow core's lead and mark the "Range (float)" field as "no_ui".

Remaining tasks

User interface changes

It is no longer possible to create "Range (float)" fields from the user interface.

API changes

-

Data model changes

-

Issue fork range-3506144

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

tstoeckler created an issue. See original summary.

tstoeckler opened merge request !19

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented
Status: Active » Needs review
taran2l’s picture

taran2l
Primary language Ukrainian
Location Lviv
commented

that one looks good to me

  • taran2l committed 20572496 on 8.x-1.x authored by tstoeckler 
    Issue #3506144 by tstoeckler: Mark "Range (float)" field as "no_ui"
taran2l’s picture

taran2l
Primary language Ukrainian
Location Lviv
commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.