question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] Inconsistence in the meta properties fallbacks in widgets

See original GitHub issue

Description

In the input widget, when the defaultText is updated, the bindings all update. However, when we clear out the text in the input widget, the bindings propagate as empty text. This is not consistent in the date picker widget. The defaultDate is always a fallback when the date is cleared from the widget.

There are two solutions here:

  • We should make this consistent by making sure that all meta properties behave like they do in the datepicker widget’s defaultDate. (fallback to default values if they exist)
  • Or fix this for the date picker widget.

Steps to reproduce the behaviour:

Add steps to reproduce this behaviour, include console / network logs & screenshots

  1. Add an input widget and a datepicker widget. Add defaultText and defaultDate respectively in the property panes
  2. Add two text widgets, each binding to the input widget’s text and datepicker’s selectedDate respectively.
  3. Try changing the text widget by making it empty and clearing the date from the date picker widget.
  4. See error

Important Details

  • Release 1.4.9

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
somangshucommented, Apr 20, 2021

In the favor of consistency, we will be going ahead and make changes to the datepicker widget. On clearing the input value, it shouldn’t fall back to the default value.

1reaction
hawisizucommented, Apr 19, 2021

In my opinion it’s the 2nd option the correct one.

The 1st one would be a nightmare: that would mean that if you remove the text from an input, you reset to the value it had before, this is non sense. If you do that it means you do want to clear the value, not reset it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Creating forms from models - Django documentation
Use a custom form field or widget if you're designing an API and want the default fallback behavior for a field that uses...
Read more >
open-stage-control/CHANGELOG.v0.md at master - GitHub
bug fixes: multiclient sync not working when targets is empty; widgets: missing target property for plots/* widgets, required for MIDI bindings; editor: set ......
Read more >
stop() - Rocket Software Documentation
More Properties (Widget Properties) ... Fallback Searching for Library Objects ... Data Error Handling in Web Applications · Data Paging in Web Applications....
Read more >
Bug listing with status RESOLVED with resolution OBSOLETE ...
Bug :1523 - "[IDEA] Offload work by distributing trivial ebuild maintenance to ... Bug:75665 - "Jelly-Tags metapackage" status:RESOLVED resolution:OBSOLETE ...
Read more >
Safari Technology Preview Release Notes - Apple Developer
Note: Shared Tab Groups and syncing for Tab Groups, Website Settings, and Web Extensions are not enabled in this release. WebAssembly. Fixed error...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found