Compilation errors on the generated code. about gwt-api-generator HOT 11 CLOSED

It's a Polymer comment change in paper-button.html (line 174) that causes this issue:

before:
@param {{node: Object}} detail Contains the animated node.

now:
Event param: {{node: Object}} detail Contains the animated node.

It seems that the missing @param annotation causes the extension of the TransitionendEventto TransitionendEventparamnodeObjectdetailContainstheanimatednode.Event

from gwt-api-generator.

Fixed in ecb419c

from gwt-api-generator.

I am not committer to this project.
But if you are going for the latest polymer version then download the components manually with bower, fix this line and generate the wrapper classes.

$ bower install --save PolymerElements/paper-elements
$ gwt-api-generator

from gwt-api-generator.

I can verify the same compilation errors. I did the following steps in an empty test directory.

bower install paper-elements
gwt-api-generator --pom
mvn package

Could you @manolo take a look at this?

from gwt-api-generator.

Yes, the basic sample from the README does not work anymore :

$ gwt-api-generator --package=PolymerElements/paper-elements --pom
$ mvn package

returns the same errors. I'd love to help to get this fixed if @manolo could provide some pointers ?

from gwt-api-generator.

Can we be a bit more forgiving for this kind of errors in the comments when generating ?
@muelbr can you past a link to the relevant part of the generator code ?

from gwt-api-generator.

As a note, the Polymer team changed from @param to Event param due to compiler issues:
PolymerElements/paper-button@2f44db5

Basically, I think the "name" function (at least for events) needs to take newlines into account.

It doesn't make sense that an event name would span multiple lines.

from gwt-api-generator.

@komasoftware Using a split on newlines and taking the first line seems to fix the issue.
(Granted, the event's generated NAME string still has the long comment nonsense with only this change in camelCase, so probably making the same change with other functions)

In helpers.js line 61:

  camelCase: function(s) {
    return (s.split('\n')[0] || '').replace(/^Polymer\./, '').replace(/[^\-\w\.]/g,'').replace(/(\b|-|\.)\w/g, function (m) {
      return m.toUpperCase().replace(/[-\.]/g, '');
    });
  },

from gwt-api-generator.

Back here. The change did not really solve the issue.

Wondering if @manolo still plans to support this library. Otherwise I need to look into another solution and rewrite my code. I would really like to know !

from gwt-api-generator.

I used an awful solution.
The solution of helpers.js line 61 dind't work for me, so i changed it to

camelCase: function(s) {
    if (s.toLowerCase().startsWith('transitionend')){
        console.log('name--:' + s);
        return 'Transitionend';
    }   
    return (s || '').replace(/^Polymer\./, '').replace(/[^\-\w\.]/g,'').replace(/(\b|-|\.)\w/g, function (m) {
        return m.toUpperCase().replace(/[-\.]/g, '');
    });
}

It's horrible, but it compiles. Then i had to use the fix mentioned here.

The problem I have now is that in Chrome the PaperInput does not work. It is visible, but i can't get the focus.
Anyone with the same problem? Could it have to do with the change i made in the function camelCase?

For what i could see, the compilation now is showing a lot of errors/warnings (?) like this one but with many components
Behavior Polymer.Templatizer not found when mixing properties into vaadin-infinite-scroller!
Any idea why this could be? Could this be the problem?

from gwt-api-generator.

How can I "npm install -g vaadin/gwt-api-generator" a specific commit ecb419c ?
Or will a new release soon follow ?

Thx for all the work !

from gwt-api-generator.