Comments (7)
Okay. This is very good point. I thought using Storybook for Mantra apps. But, this is other way around and very interesting.
I think I kind a like it. Will work on it.
from storybook.
@sammkj Now we use Mantra.
More info here.
from storybook.
Yes it is.
I think we should thinking to rebrand Mantra as an architecture for React. Let's have a chat on the Mantra forum. (What I am planning to do in the early next week)
from storybook.
Storybook is gaining more and more attention. With mantra structure, other devs can work on new features (mantra module) and distribute it to npm. Then storybook users can just npm install react-storybook-[feature]
and boom! [feature]
is added. But normally features would require a layout change. For example, adding a resizer would certainly change the layout. I'm not sure how we can approach this smoothly.
from storybook.
Yes. I get it. That's really good.
from storybook.
Hope we can close this now.
from storybook.
I have some problems with @storybook/mantra-core
I have a meteor v1.6.1 app, with [email protected]. But I have a problem with the composeWithTracker function. This function have been taken off react-komposer@2, used by storybook, but is still declared in /dist/index. So, I have a question. How could I send data from my containers to my components? Need help please.
When I do this in my container with :
import {useDeps, composeWithTracker, composeAll} from '';
export const classeComposer = ({context}, onData) =>{
const {Meteor, FlowRouter, Collections,} = context();
if (Meteor.subscribe('classes.list').ready()){
const lesClasses = Collections.Classes.find({},
{fields: {_id:1, code:1, nbrePlaces:1},
sort: {code:1, nbrePlaces:1}}).fetch();
const nbreClasses = Collections.Classes.find({}).count();
onData(null, { lesClasses, nbreClasses});
}else{
onData();
}
};
export const classeMapper = (context, actions) => ({
addclasse: actions.classes.addclasse,
updateclasse: actions.classes.updateclasse,
deleteclasse: actions.classes.deleteclasse,
context: () => context
});
export default (component) => composeAll(
composeWithTracker(classeComposer),
useDeps(classeMapper)
)(component);
I have this error in my consol:
Uncaught (in promise) TypeError: composeWithTracker is not a function
at eval (/imports/modules/core/containers/Classes.js:88:21)
at Route._callee$ (http://localhost:4000/app/app.js?hash=9e577aa13e8896245acee791ed37df88948a09c2:381:32)
at tryCatch (http://localhost:4000/packages/modules.js?hash=5763c96b3eee7f2b55565963c705a396d19a512b:34210:40)
at Generator.invoke [as _invoke] (http://localhost:4000/packages/modules.js?hash=5763c96b3eee7f2b55565963c705a396d19a512b:34444:22)
at Generator.prototype.(anonymous function) [as next] (http://localhost:4000/packages/modules.js?hash=5763c96b3eee7f2b55565963c705a396d19a512b:34262:21)
at tryCatch (http://localhost:4000/packages/modules.js?hash=5763c96b3eee7f2b55565963c705a396d19a512b:34210:40)
at invoke (http://localhost:4000/packages/modules.js?hash=5763c96b3eee7f2b55565963c705a396d19a512b:34300:20)
at http://localhost:4000/packages/modules.js?hash=5763c96b3eee7f2b55565963c705a396d19a512b:34310:13
at http://localhost:4000/packages/meteor.js?hash=b0f12795c8cc1423b5850502871996903f947ed5:1167:22
at
Need help please.
from storybook.
Related Issues (20)
- [Bug]: `csf-plugin` fails to read stories with names not matching hardcoded regex HOT 2
- [Bug]: findBy* not working properly in story steps (Angular 17)
- [Bug]: `options: any[]` in argTypes is not sufficient HOT 7
- [Bug]: jsxDEV is not a function on production build with @storybook/react-vite 8.0.7
- [Bug]: viteConfigPath has wrong types.
- [Bug]: Custom .mdx stories not showing code snippet anymore
- [Documentation]: Configure the testing framework for portable stories (With Jest)
- [Bug]: Error installing 7.6.18 HOT 6
- [Bug]: Inconsistent action log when action argument is falsy HOT 1
- [Bug]: The modulesCount cache is writing to disk too much
- [Bug]: error npm install @storybook/[email protected] HOT 1
- [Bug]: Can not install @storybook/node-logger on yarn v3,v4 HOT 4
- [Bug]: toHaveBeenCalledWith does not display expected / received values on failure HOT 1
- [Bug]: Storybook and Radix-vue memory leak
- [Bug]: Can't use enum from external file HOT 1
- [Bug]: can't pass tags array to CSF default export when is generated from a function (v7 AND v8)
- [Bug]: Storybook-build failing on Angular 17 HOT 1
- [Bug]: auto docs doesn't build in static-storybook 8
- [Bug]: chrome / VS Code debugger not working correctly with Storybook 8 (Vite / React) HOT 1
- [Bug]: `@storybook/test` breaks react-native storybook HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from storybook.