It says there is good resources and the first title on the landing page says that those practices are bad and should not be used any more. Maybe find something else to link to make that point?

We need a contributing.md doc that shares community conventions.

Stamp conventions

• Naming stamps: your-module-name-stamp
• Keywords for package.json: stamp, stampit

Automatic code quality conventions 😎

• Use the prod-module-boilerplate (soon to be replaced with `npm install -g cloverfield cf-package

I really like the idea of this project -- I think there's a lot of room for making animation in react simpler. However, I think you need better documentation / examples. I tried using this in a project I'm working on today and for the life of me I couldn't get it working. The cloned repo and example worked fine -- but when I tried to apply it to my own code... well, nothing worked.

It'd be nice

I think it would be useful to add a mention about Async streams (IAsyncEnumerable) when a developer wants to tackle 'Handle streams of data' problem.

when the label in the link is not in the current frame no effect will be seen.

The frame that contains the label should be made active.

if there are more than one label with the same name we should scroll to all of them.

IMPORTANT: this issue doesn’t have high priority. If this is too complex to implement we should discuss if there is an easy solution.

Add a window about the program
This step allows users to identify project information, host new contributors, and even an error reporting button and a donation button

This temporary documentation repo is meant for testing out the new doc toolchain to provide better cross-package navigation and a (hopefully) generally improved experience... This doc repo consist of over 8000 markdown files and I cannot check them all myself for issues (of which there are still many

Description

To bring it in-line with the other Crocks we need to add in descriptive documentation for the List crock with examples

Task List

• Add main List.md file to 'docs/src/pages/docs/crocks/' based on the others
• Ensure it has the correct 'weight'
• Locate all references to List and update it to link to the new List documentation. Reference the section

In traditional 'state machines' usually, there is a way to disallow a transition. Perhaps based on business rules, consider the example of a cash register state machine.

You may have a cash register that starts with $100 in it. You may have a 'withdraw' action that lets you take money out. How would you prevent the following scenario:

CashRegister
  .balance.withdraw(20)
  .

What:

Attaching a ref to Composition results in a warning:

Warning: Function components cannot be given refs. Attempts to access this ref will fail. Did you mean to use React.forwardRef()?

Why:

Composition does not use React.forwardRef

• atomic-layout version: ^0.13.0-alpha.2

I am by far the least qualified person to review your work, but I find it relentlessly fascinating. I want your work to gain more traction, but I think that English is not your first language. I would like to offer my help to do some editing on your FP-complete posts to make them sound more natural in English. I can't offer much, but as I read through them I could offer some edits/questions that m

Is your feature request related to a problem? Please describe.
If this is something seen as useful to the userland, I'd like to possibly look into applying readable classnames for @chakra-ui/vue components in the future. This could be an opt-in feature.

Currently, chakra-ui/vue components output CSS classnames for each component as such:

/* Some weird non-descriptive class name 

Some methods have been introduced later. Right now lint doesn't warn for such calls. It warns for AppCompatActivity but not for CompositeActivity. I.e. Activity#isDestroyedI()

The @RequiresApi annotation could be added for such methods. It could be generated by the platform-tools/api/api-versions.xml which is used for lint warnings.

Description

The current docs generated with Jazzy show only the methods that a class declares itself, but not the ones inherited from superclass or superclass conformance extensions. For instance, Id shows only 5 methods, but ForId conforms to a number of typeclasses that add methods to `

Hi

Regarding this pull request jfairbank/revalidate#46

I expect the following code to work :

export const passwordFieldValidator = composeValidators(
	isRequired({
		id: 'error.password.required',
		description: 'Error message password required',
		defaultMessage: 'You must provide a password'
	}),
	hasLengthGreaterThan(5)(
		id: 'error.password.requ

We were experiencing a lot of timeout issues with services and compoxure felt really slow. I just found that upping the UV_THREADPOOL_SIZE variable really speeds things up a lot. I guess it would be a good idea to document this, and of course I'm now wondering if there are other things that can speed up compoxure as well?

The docs do not show an example of resolveDependees. I am getting an error when trying to create a resolver the following way:

const poolShareValue = pipeResolvers(
  resolveDependees(['totalPoolShares', 'poolValue']),
  ([totalPoolShares, poolValue]) => {
    const ethPerShare = totalPoolShares.toNumber() > 0 ? parseFloat(utils.formatEther(poolValue)) / totalPoolShares.toNumber() :