It is less familiar, but give it a shot! If the community finds it hard to
work with I think that'd be an important signal. My suspicion is that it
will make things easier and not harder on balance for contributors but I'm
willing to update based on evidence :)
On Tue, May 24, 2016 at 4:12 PM,
I would argue that it lowers the barrier to entry for new people. There's a
little bit of syntax that could be distracting, but with an editor that has
typescript support, you can dive into a function and instantly know that
types the arguments have. I often spend huge amounts of time tracing back
This is probably the most polymer your demo can be...
note: I fixed the imports to use polygit and removed your search button
completely
This can probably be more efficient, I needed a distraction from work so I
tweaked things for you ;)
http://plnkr.co/edit/Qzky7tpvGjNXu8Tt77hw?p=preview
First of all, thanks for your answers! It's cool that you're taking the
time to discuss this.
Being a fully open source project I like to see Polymer as a community
effort, even if the vast majority of contributions come from the core team.
I agree that the use of typescript might not affect
I second that. For our node-based tools, the decision to go with typescript
was very straightforward. Our use of typescript has no impact on anyone
downstream, whether they use the tools as libraries or as binaries, as by
the time the code is published in npm it's totally normal, legible,
Thank you for the feedback.
Le mardi 24 mai 2016 21:27:01 UTC+2, Justin Fagnani a écrit :
>
>
> On Tue, May 24, 2016 at 12:02 PM, Nicolas Ocquidant > wrote:
>
>> If I had understood correctly, managing imports in one big html file for
>> the entire app (for instance
On Tue, May 24, 2016 at 12:02 PM, Nicolas Ocquidant
wrote:
> If I had understood correctly, managing imports in one big html file for
> the entire app (for instance elements.html) is not a best practice anymore.
> Indeed, PRPL and polymer-cli requires each component (or
Using TypeScript in tool has really helped our development process - from
documentation, refactoring, and code-completion, to the type checking and
errors that compliments our tests. We've been converting our tools projects
to TypeScript for months now, so this is nothing new.
There are extremely
If I had understood correctly, managing imports in one big html file for
the entire app (for instance elements.html) is not a best practice anymore.
Indeed, PRPL and polymer-cli requires each component (or view) to manage
its dependencies.
Unfortunately, IDE are not a great help here. Do you
Personally, I am a bit ambivalent towards Typescript.
On one hand I like the types system helping me during development; but on the
other, like you, I like to use the language of the platform natively to
prevent weirdness in machine-written code that is less understandable to a
human reader.
I mean nothing against Typescript but after all the talk at I/O about
sticking to standards and reducing the amount of necessary tooling, whoever
thought this was a good idea? I understand that there are a lot of things
that speak for Typescript in general but I haven't seen it used anywhere
By any chance do you have a gulpfile?
On Tue, May 24, 2016 at 4:08 AM, Marco Stolle
wrote:
> Hello
>
> i'm trying the new polymer-cli, everything works but when i try to build i
> get the error
>
> Error: Cannot find module 'gulp'
>
>
> gulp is installed global and local
Hello
i'm trying the new polymer-cli, everything works but when i try to build i
get the error
Error: Cannot find module 'gulp'
gulp is installed global and local
gulp --version = 3.9.1
searched Google and this forum but no results
Any ideas?
thanks
Marco
Follow Polymer on
13 matches
Mail list logo