saveTiddler should auto-merge defaultCustomFields

[FND]

A recent post[1] made me aware that TiddlyWiki's `saveTiddler` method
does not currently merge `config.defaultCustomFields`.

However, I seem to recall that we'd agreed it should do that a long time
ago (can't find the thread/ticket/conversation now, unfortunately).

Can anyone enlighten me what the current status is (also with core
development in general)?

-- F.

[1]
http://groups.google.com/group/tiddlywikidev/browse_thread/thread/af3073f84abe877e/cd0e1776fc55c492?#cd0e1776fc55c492

[Tobias Beer]

This sounds like a very appreciated change.
Much better than each individual plugin doing exactly that for
tiddlyspace compatibility.
Please get this rolling.

Cheers, Tobias.

[PMario]

+1

[Måns]

+2 :-)

[Martin Budden]

When we moved from subversion/trac to github we deliberately didn't
move over all the tickets. The view being that if anyone was
sufficiently interested in a feature or fix, then they would raise an
issue in github.

I'm quite happy to put this in the next release.

To answer your question about core development: in general the best
way to get a feature or bug fix is to raise it as an issue on github,
https://github.com/TiddlyWiki/tiddlywiki/

Postings in this group will normally be picked up, but can be more
easily missed or overlooked (or could be subject to the "can't find
the thread/discussion" problem).
A +1 or +2, of course, indicates that the feature is wanted - but
again it makes things easier if an issue is raised. And an issue with
a patch or merge request and test code is even better.

[FND]

> raise an issue in github

I've started to get the ball rolling:
https://github.com/TiddlyWiki/tiddlywiki/issues/55
https://github.com/TiddlyWiki/tiddlywiki/pull/56
(note the pull request's message though)

-- F.