Menu
Effector LogoEffectorDocsAPIBlogTry
ChangelogTwitterGitHub
Effector LogoEffector
  • Docs
  • API
  • Blog
  • Try
  • Changelog
  • Twitter
  • GitHub
Effector LogoEffector
  • Introduction
    • Installation
    • Core Concepts
    • Glossary
    • Prior Art
  • API
    • effector
      • API Reference
      • Unit creators
        • createStore
        • createEvent
        • createEffect
        • createDomain
      • Unit definitions
        • Event
        • Store
        • Effect
        • Domain
      • combine
      • restore
      • createApi
      • sample
      • guard
      • attach
      • merge
      • split
      • forward
      • is
      • fromObservable
      • createStoreObject
      • clearNode
    • effector-react
      • API Reference
      • Hooks
        • useStore
        • useStoreMap
        • useList
        • useGate
      • createComponent
      • Gate
      • createGate
      • createStoreConsumer
    • effector-vue
      • API Reference
      • VueEffector
      • ComponentOptions
      • Vue
  • Conventions
    • Naming
    • Best practices
  • Recipes
    • Recipes
    • Usage with TypeScript
    • React
      • Example
      • Effects
      • Forms
      • Gate - a bridge between props and store
      • TODO creator
      • Dynamic form schema
      • Countdown timer
    • React Native
      • React Native Example
  • Advanced guide
    • Computation priority
  • FAQ
    • FAQ

FAQ

#Why do we can give names in events, effects and etc ?

This will help in the future in the development of the effector devtools, and now it is used in the playground on the left side bar.
If you don't want to do it, you can use the babel plugin. It will automatically take the name for events and effects from the variable name.

Previous

« Computation priority

  • Why do we can give names in events, effects and etc ?

Docs

  • Docs
  • API
  • Changelog

Community

  • Twitter
  • Telegram 🇷🇺
  • Telegram

More

  • Github
Effector - the state manager
Copyright © 2020 zerobias