Eemeli Aro
Eemeli Aro
I agree. I'm working on an update to how items are filtered by date and time, which should fix this. Effectively, the new default will be to hide all events...
Effectively, you're asking for "My con" to be an additional filter choice alongside tags etc, thugh placed separately in the menu structure. I'm not convinced of the usefulness of such...
Maybe I'm missing something, but starting from the example in https://github.com/tc39/proposal-extractors/issues/15#issuecomment-2037675151, wouldn't something like this be much simpler and already possible? ```js let x1 = line.p1.x; let y1 = line.p1.y;...
I presume that this PR will be rebased after #84 is merged, as it currently appears to contain its changes as well?
Why do we want this?
The question isn't silly at all, and generalises to "What happens when explicit tag resolution fails?" `!!bool maybe` is a pretty good example to use here, as boolean values can...
While looking through @Thom1729's PR on this, I realised that we have an even greater imprecision we need to fix: Nothing in the Core Schema spec actually defines how `!!bool...
In case it's of interest, here's the mapping I used to generate `data.json` from the previous `allCountries` data: ```js const data = allCountries.reduce( (data, [name, iso2, dial, format, prio, areas])...
The package.json file marks the license as MIT.
Sorry, not going to be able to do that anytime soon. Your commit 296922d reformatted everything, so it isn't possible to apply any earlier PRs without manually recreating them from...