Getting started for a new extern #1

Activity

1. fantoine commented on May 22, 2016

   

   fantoine

   on May 22, 2016

   Contributor

   More actions

   Hi, currently there are no guides available. However it looks like you got the whole thing in this repo. :)

   You should also add an extraParams.hxml file to specify the default version (major.minor) of the library to use (for instance).
   It let you define the version of the library to use if it's not overriden by the project configuration.
   It's only useful if your extern can be available for multiple versions of a library.

   This is the case for Validator where some methods changed in version 5.
   I use a macro constant validator_ver which is automatically defined by js.extern.Extern.
   If this value is defined in your project, so it will use it. Otherwise it will use validator_default_ver.
   The default variable constant should have this name: <module>_default_ver where module is the named specified in js.extern.Extern<'<module>'>.

   Then, your extraParams.hxml should contains:

   -D redis_default_ver=2.6

   I think it will change in the future because it's not very handy, but currently it works this way.
2. kevinresol commented on May 22, 2016

   

   kevinresol

   on May 22, 2016

   Last edited by kevinresol

   MemberAuthor

   More actions

   Yeah.

   Just one suggestion here. Now the @:externjs meta uses a list of key=value params which is slightly unnatural in my opinion. Actually we can use an anon obj to do that, for example:

   @:externjs({
     namespace: true,
     global: 'redis'
   })

   Then when you parse you just need to match a EObjectDecl and then get the fields from there.