Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meta keys stored without value #324

Open
ThomasWaldmann opened this issue Feb 10, 2013 · 3 comments
Open

meta keys stored without value #324

ThomasWaldmann opened this issue Feb 10, 2013 · 3 comments
Labels
bug Something isn't working prio3 normal prio

Comments

@ThomasWaldmann
Copy link
Member

Original report by xiaq (Bitbucket: xiaq, GitHub: xiaq).


Thomas Waldmann created an issue 2012-08-14

it seems to store superseded_by, depends_on, ... even if they have no value (it stores an empty string then).

is this the best way we can deal with that? maybe not store the key if there is no value?

btw: it doesn't store the priority/severity/... if they have no value.

@ThomasWaldmann
Copy link
Member Author

Original comment by xiaq (Bitbucket: xiaq, GitHub: xiaq).


there seems to be no trivial way around this...

for a distinction in the Flatland MetaForm, there needs to be a distinction in the http request. for a distinction in http request, there needs to be a distinction in the html form.

perhaps take a look at html5 form enhancements and/or form helpers from javascript libraries...

@ThomasWaldmann ThomasWaldmann added prio3 normal prio bug Something isn't working 2.0.0a0 and removed 2.0.0a0 labels Aug 26, 2018
@ThomasWaldmann
Copy link
Member Author

see #618.

@RogerHaase
Copy link
Member

The superseded_by, depends_on meta keys in the original post are used by Tickets (see #576). #785 is also related to issue of whether keys with "empty" values should be in metadata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working prio3 normal prio
Projects
None yet
Development

No branches or pull requests

2 participants