Expected behavior

In the Choo docs on Routing, in the section "Listening for Route Changes" implementing:

var html = require('choo/html')
var choo = require('choo')
var app = choo()

var app = choo()
app.use((state, emitter) => {            // 1.
  emitter.on('navigate', (route) => {    // 2.
    console.log(`Navigated to ${route}`) // 3.
  })
})

Should return a conso

Hello, I am a developer from China. I like this library very much and have translated the documentation, hoping to better recommend it to the majority of Chinese developers.

Here is the link

I hope you can put it into the official document.

PS. 中文文档 means Chinese Documentation

Thank you

Related to #781 and #517.

As described in #781, Feign overrides the timeouts configured in my Apache RequestConfig, even if I don't set custom request options in the Feign builder. This is unexpected behavior.

The change introduced to fix #517 copies the existing RequestConfig, but then immediately overwrites the timeouts, again, even if no Feign request options are set.

Hey everyone !

In order for the new website to happen, we need to define some sort of branding for Iced. Since this should be a community effort, here are my first thoughts / mind map of how I reasoned about the logo and color scheme.

Logo

What is Iced ?

• GUI Framework
• Platform-agnostic
• Written in Rust
• Elm Architecture

What does iced mean ?

• Ice
  • Ice

you may want to update/remove the link to

libi.io
http://libi.io/library/1683/django-jet
as it is broken and bring to GoDaddy.

One of the most hated provider in the world! 👯‍♂
Cheers

Users need to be aware that there are two interfaces with different use cases in mind.

See: ansible-community/ara#85

Version 2 Checklist

Documentation

• Rewrite version 2 docs to reflect updates
• Rewrite version 2 docs in nuxt (and maybe markdown)
• Add guide for writing tests

Fixes

• allow data with DELETE
• Fix polluted params issue when where params send twice

Enhancements

• api renamed to http
• rename apiConfig to httpConfig

It would be nice to add all of the cli usage options in the usage section of the documentation.

For example, it says this:

Port Selection: Automatic detection and use of an open port (if the specified one is in use)

but how to actually specify a port is not documented.

*******************>>> should be on
$(document).one('receivelexconfig', function onReceiveLexConfig() {
var localTimeZone;
try {
localTimeZone = JSON.stringify(
Intl.DateTimeFormat().resolvedOptions().timeZone
);
} catch (err) {
localTimeZone = JSON.stringify(
new Date().getTimezoneOffse

Blinking LED

How to make a led blink depending on its value

css:

/* Do the maths here to keep css as clean as possible */
/* Assigned variables are available to the formulas that come after */
#{
    threshold = 0.5;
    value = @{this};
    animationCount = value >= threshold ? "infinite": "0";
}

/* animation names are not scoped to the widget only and can be

We would like to be able to make interface and method ‘documentation’ comments available to templates.

For example, we would like to use a method comment to provide hints to a logging decorator about what and how to log specific params and results (avoiding monolithic log output, hiding sensitive data etc)

The documentary comments are readily available in the ast and so could be copied to

The current documentation in the Wiki is incomplete and mainly example-based. At least I was unable to find any information on the full API and or JSON content of meta.json in the various places. Even more simple: CK uses 'module', 'package', 'soft', 'program' and a plethora of others without a clear overview or definition what they are and how they related to each other.

Even the existing exam