Skip to content

To specify an error message explicitly for uppercase - #33

Open
ggikko wants to merge 2 commits into
square:masterfrom
ggikko:feature/ggikko
Open

To specify an error message explicitly for uppercase#33
ggikko wants to merge 2 commits into
square:masterfrom
ggikko:feature/ggikko

Conversation

@ggikko

Copy link
Copy Markdown

fix for issue #32

@pforhan

Copy link
Copy Markdown
Contributor

Add a test case too?

@ggikko

Copy link
Copy Markdown
Author

I added test case for uppercase.

I thought that this test case is useless cause there's already illegalTokenCharactersFailFast test case. it's very similar..

@pforhanpforhan mentioned this pull request Jul 19, 2017
from("Hello {Name}").putOptional("Name", "Eric").format().toString();
fail("Expected IllegalArgumentException");
} catch (IllegalArgumentException e) {
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the key here is to verify that the value of e.getMessage() is not Missing Closing Brace

pforhan added a commit to pforhan/phrase that referenced this pull request Jul 21, 2017
Tweaks invalid start- and end-of-token messages for clarity.
Inspired by square#33, fixessquare#32 and square#34, probably square#29 as well.
pforhan added a commit to pforhan/phrase that referenced this pull request Jul 21, 2017
Tweaks invalid start- and end-of-token messages for clarity.
Inspired by square#33, fixessquare#32 and square#34, probably square#29 as well.
pforhan added a commit to pforhan/phrase that referenced this pull request Jul 26, 2017
Tweaks invalid start- and end-of-token messages for clarity.
Inspired by square#33, fixessquare#32 and square#34, probably square#29 as well.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ggikko@pforhan