search

duckAsteroid / protobuf-dt

Automatically exported from code.google.com/p/protobuf-dt
0 stars 0 forks source link

Custom options create temporary errors #136

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. create a proto file that uses custom options (see attached image)
2. use an option field in an error free proto file
3. the file has numerous errors when you edit the option field

What is the expected output? What do you see instead?
I expect the option field use to be validated correctly.  Indicating when there 
are errors and indicating when the file is valid

What version of the product are you using? On what operating system?
I am testing a 1.09 version from Ben Wright on Windows 7 64 bit 

Please provide any additional information below.

Attached images

Original issue reported on code.google.com by moofis...@gmail.com on 16 Oct 2011 at 10:11

Attachments:

GoogleCodeExporter commented 9 years ago 
Sorry I forgot to mention that if I click outside the text editor (say in that 
maven repo view on the bottom of the images) the correct behavior occurs.

Original comment by moofis...@gmail.com on 16 Oct 2011 at 10:14

GoogleCodeExporter commented 9 years ago 
I've also been having this issue with the changes I posted for patch 111 - I 
have yet to spend enough time tracking down the chain of events in XText that 
leads to this but it is pretty consistent in having spurious errors until a 
second validation occurs.

My only guess so far is that the ResourceSet is not complete during the first 
validation so imported files are not being properly considered...

Original comment by compuwar...@gmail.com on 17 Oct 2011 at 4:18

GoogleCodeExporter commented 9 years ago

Original comment by alr...@google.com on 18 Oct 2011 at 11:23

GoogleCodeExporter commented 9 years ago 
Mike still sees this error.

Original comment by alr...@google.com on 20 Oct 2011 at 8:27

GoogleCodeExporter commented 9 years ago

Original comment by alr...@google.com on 20 Oct 2011 at 10:41

GoogleCodeExporter commented 9 years ago

Original comment by alr...@google.com on 3 Nov 2011 at 1:06

GoogleCodeExporter commented 9 years ago

Original comment by alr...@google.com on 13 Jan 2012 at 3:20

GoogleCodeExporter commented 9 years ago 
It seems this issue has been fixed in latest (v1.2.2.)

Original comment by alr...@google.com on 4 Mar 2012 at 3:50