This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 230401 - YAML indentation requires to be consistent, developer can easily break YAML file without indentation discovery
Summary: YAML indentation requires to be consistent, developer can easily break YAML f...
Status: RESOLVED DUPLICATE of bug 212063
Alias: None
Product: web
Classification: Unclassified
Component: YAML (show other bugs)
Version: 7.3
Hardware: PC Other
: P3 normal (vote)
Assignee: Petr Pisl
Depends on:
Reported: 2013-05-28 16:53 UTC by turneliusz
Modified: 2013-07-02 14:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description turneliusz 2013-05-28 16:53:11 UTC
When project settings and YAML identation style are different developer can easily break someones YAML file.

Example: IDE uses tabs, YAML file uses spaces. Developer uses tabs in his YAML file, it seems to him that everything is fine, the indentation is consistent - but not for his application parser who sees a tab as one character (not a set of 4-8 characters depending on developer style).

This behaviour can be considered as defect because IDE is already checking syntax and is not noticing the problem. Maybe I'm missing something. The problem occurs to me really all the time and it casuses a lot of headaches when a valid-looking YAML file is really not parsable by application. Please help :)
Comment 1 Ondrej Brejla 2013-07-02 14:14:12 UTC
Probably 2 issues:

1) "YAML" should be added to Options -> Editor -> Formatting -> Language, so one can set a proper behavior per project (Project properties -> Formatting).

2) These "tab/space" inconsistances could be catched by a parser...NB uses external one...which has more problems. It should be replaced.

First issue is an enhancement (I filled new issue #232157) and the second is a duplicate of issue #212063


*** This bug has been marked as a duplicate of bug 212063 ***