Bugzilla – Full Text Bug Listing
| Summary: | ProposalProvider does not propose braces if using xbase | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Andreas Muelder <Andreas.Muelder> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | sven.efftinge |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
The reason for that is the method XBaseProposalProvider#isKeywordWorthyToPropose() It filters all keywords with a length <= 1. What is the intention for that? Overriding this method in my own ProposalProvider does work for me. Sorry, I forgot about it. Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |
Build Identifier: 20110916-0149 If a grammar is derived from XBase, the proposal provider does not provide braces anymore. ( '{', '(', '[' .... ) Reproducible: Always Steps to Reproduce: 1. Create a new Grammar derived from XBase: 2. Create a simple model Model: {Model} 'model' '{' '}' ; 3. In the runtime editor, put the cursor after 'model' and hit CTRL + space