-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(cmf): simplify imports #1359
Conversation
'getCollection', | ||
'dispatch', | ||
'dispatchActionCreator', | ||
]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
moved in constant
1 similar comment
…/ui into jmfrancois/chore/cmf-api-to-index
docs/_posts/2017-02-28-api-action.md
Outdated
@@ -80,11 +81,11 @@ api.action.getOnProps(props); | |||
|
|||
It returns the array of props keys beginning with `on`. This is used to get the list of action props (onClick, onKeyDown, ...). | |||
|
|||
## mapDispatchToProps | |||
## mapDispatchToProps (DEPRECATED) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if deprecated please remove doc to avoid people to keep using it
docs/_posts/2017-02-28-api-action.md
Outdated
@@ -67,11 +68,11 @@ It creates the action to dispatch from | |||
* the provided user `event` | |||
* the provided user `data` | |||
|
|||
## getOnProps | |||
## getOnProps (DEPRECATED) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if deprecated please remove doc to avoid people to keep using it
docs/_posts/2017-02-28-api-action.md
Outdated
@@ -47,11 +48,11 @@ api.action.getActionInfo(context, id); | |||
|
|||
It returns the static `action` definition from the settings. | |||
|
|||
## getActionObject | |||
## getActionObject (DEPRECATED) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if deprecated please remove doc to avoid people to keep using it
docs/_posts/2017-02-28-api-action.md
Outdated
@@ -33,11 +34,11 @@ api.actionCreator.get(context, id); | |||
|
|||
It returns the registered `action creator` from the provided registry. | |||
|
|||
## getActionInfo | |||
## getActionInfo (DEPRECATED) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if deprecated please remove doc to avoid people to keep using it
docs/_posts/2017-02-28-api-action.md
Outdated
@@ -6,11 +6,12 @@ date: 2017-02-28 22:10:38 | |||
order: 3 | |||
--- | |||
|
|||
## getActionsById | |||
## getActionsById (DEPRECATED) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if deprecated please remove doc to avoid people to keep using it
…/ui into jmfrancois/chore/cmf-api-to-index
What is the problem this PR is trying to solve?
having api create more troubles than it solves anything.
The first idea of { api } was to expose only what the developer needs.
We are in progress to make cmf a framework and so we need to make import simple and easy to understand.
What is the chosen solution to this problem?
So no more { api } just index, so all the things are accessible from index and more and more we will remove all deprecated stuff in the following PRs.
Let's introduce the default export 'cmf':
This will replace { api } and provide more and less stuff;
the next step is #1293 (bootstrap)
Please check if the PR fulfills these requirements
[ ] This PR introduces a breaking change