Ticket #1282 (closed defect: wontfix)

Opened 2 years ago

Last modified 2 years ago

Apply defaultCustomFields when saving a tiddler

Reported by: jayfresh Owned by: JeremyRuston
Priority: major Milestone: 2.6.3
Component: core Version:
Severity: medium Keywords: defaultCustomFields saveTiddler
Cc:

Description

See  https://github.com/TiddlySpace/tiddlyspace/issues#issue/491

It doesn't make sense to me that defaultCustomFields need to be added manually by the caller of saveTiddler - my opinion is that they ought to be merged in to the provided fields object. Otherwise, they are not default.

Change History

Changed 2 years ago by FND

  • priority changed from undefined to major
  • severity changed from undefined to medium
  • milestone set to 2.6.3

Changed 2 years ago by MartinBudden

  • status changed from new to closed
  • resolution set to wontfix

Default values are values that are used when nothing is specified when the tiddler is created. They are not to set unspecified values when saving.

Also, from a users perspective, the current system allows them to use defaultCustomFields if they wish, but if defaultCustomFields were automatically merged when saving then it would be a bit of a pain for users who did not want to use them - they'd have to save defaultCustomFields, set them to null and then restore them.

Won't fix.

Note: See TracTickets for help on using tickets.