Skip to content
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.

Parse errors in global.json need line number and file name #1081

Closed
davidfowl opened this issue Jan 16, 2015 · 0 comments
Closed

Parse errors in global.json need line number and file name #1081

davidfowl opened this issue Jan 16, 2015 · 0 comments
Assignees
@davidfowl
Labels
3 - Done bug
Milestone
1.0.0-beta3

Comments

@davidfowl
Copy link
Member

No description provided.

@davidfowl davidfowl added the bug label Jan 16, 2015
@davidfowl davidfowl self-assigned this Jan 16, 2015
@davidfowl davidfowl added this to the 1.0.0-beta3 milestone Jan 16, 2015
davidfowl added a commit that referenced this issue Jan 18, 2015
@davidfowl
Return global.json errors to DTH
b926392 
- Renamed ProjectFormatException to FileFormatException
- Handle errors in global.json with line numbers and file names as well

#1081
@davidfowl davidfowl mentioned this issue Jan 18, 2015
Merged
davidfowl added a commit that referenced this issue Jan 19, 2015
@davidfowl
Return global.json errors to DTH
c48e8d1 
- Renamed ProjectFormatException to FileFormatException
- Handle errors in global.json with line numbers and file names as well

#1081
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@davidfowl davidfowl

Labels
3 - Done bug
Projects
None yet
Milestone
1.0.0-beta3
Development

No branches or pull requests
1 participant
@davidfowl