fede-rodes / meteor-apollo-starter-kit Goto Github PK

Related: apollographql/meteor-integration#109

Your api key are probably protected by source origin, but in general, you should never publish sensitive info like api keys. PR sent: #26

I've been away from meteor for about a year and just jumping back in to check it out again. While looking for boilerplates, stumbled across yours, so hope you don't mind my injection — I see this is a n exploration repo.

Create 2 new folders to split /components folder content as follows:

/imports/ui/dumb-components

• alert
• button
• fieldset
• form
• input
• label
• loading
• message
• title
  -subtitle

/imports/ui/smart-components

• auth
  -route-wrappers

See:

https://github.com/fede-rodes/meteor-apollo-starter-kit/blob/master/imports/ui/components/route-wrappers/logged-in-route.js#L36

https://github.com/fede-rodes/meteor-apollo-starter-kit/blob/master/imports/api/user/server/resolvers/user.js#L18

https://github.com/fede-rodes/meteor-apollo-starter-kit/blob/master/imports/api/user/server/utilities.js#L23

Need to clean theme definition and usage across the app

See:
https://github.com/fede-rodes/meteor-apollo-starter-kit/blob/master/imports/ui/theme.js

Get colors/font-size from theme:
https://github.com/fede-rodes/meteor-apollo-starter-kit/blob/master/imports/ui/components/alert/index.js
https://github.com/fede-rodes/meteor-apollo-starter-kit/blob/master/imports/ui/components/button/index.js
https://github.com/fede-rodes/meteor-apollo-starter-kit/blob/master/imports/ui/components/input/index.js
https://github.com/fede-rodes/meteor-apollo-starter-kit/blob/master/imports/ui/components/label/index.js
https://github.com/fede-rodes/meteor-apollo-starter-kit/blob/master/imports/ui/components/message/index.js

In order for mergeTypes (merge-graphql-schemas) to work we needed to downgrade graphql to version 0.11.7. Once graphql 0.12.4 we'll be able to upgrade safely

Urigo/merge-graphql-schemas#111

Is there a way to define collection2 as a server-side only package? I've tried adding a copy of collection2-core into packages folder in my root app and changing the api.export directive to api.export('Collection2', ['server']); but the package is still showing in my client bundle. I guess it's tightly coupled with Minimongo?

Hello,

after a fresh clone I get a

Failed to build the storybook
ERR! ./imports/ui/components/dumb/message/index.js
ERR! Module build failed: SyntaxError: Unexpected token (24:34)
ERR!
ERR!   22 | // COMPONENT:
ERR!   23 | //------------------------------------------------------------------------------
ERR! > 24 | const Message = ({ type, content, ...rest }) => (
ERR!      |                                   ^
ERR!   25 |   content ? <Div type={type} {...rest}>{content}</Div> : null
ERR!   26 | );
ERR!   27 |
ERR!
ERR! BabelLoaderError: SyntaxError: Unexpected token (24:34)
ERR!
ERR!   22 | // COMPONENT:
ERR!   23 | //------------------------------------------------------------------------------
ERR! > 24 | const Message = ({ type, content, ...rest }) => (
ERR!      |                                   ^
ERR!   25 |   content ? <Div type={type} {...rest}>{content}</Div> : null
ERR!   26 | );
ERR!   27 |

I am guessing that this is a babel problem, is this working for you ?

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

See:

• https://stories.betalist.com/how-to-make-email-confirmation-a-little-easier-for-your-users-b26125ce3b42)
• https://www.quora.com/Many-software-companies-ask-new-users-to-activate-their-account-by-clicking-on-a-link-in-an-email-I-feel-like-this-detracts-from-the-onboarding-experience-How-can-companies-avoid-doing-this-while-also-preventing-spammers-bots-from-signing-up
• https://github.com/bkonetzny/link-to-inbox

Take a look at:

https://blog.meteor.com/announcing-meteor-1-5-b82be66571bb
https://blog.meteor.com/meteor-1-5-react-loadable-f029a320e59c
http://thejameskyle.com/react-loadable.html
https://github.com/meteor/react-loadable-example

• take a look at workbox

TODO: need some investigation here: link to related projects

Related: ilan-schemoul/meteor-service-worker#6

Service workers in general:

• https://medium.com/@addyosmani/progressive-web-apps-with-react-js-part-i-introduction-50679aef2b12
• https://www.made-on-mars.com/blog/how-to-pwa-an-introduction-on-progressive-web-app-and-a-tutorial-to-create-one-with-full-features-push-notification-service-worker-offline-mode/
• https://github.com/NitroBAY/meteor-service-worker
• https://github.com/saurshaz/pwa-meteor/blob/master/client/serviceWorker.js
• https://developers.google.com/web/tools/workbox/
• https://youtu.be/cmGr0RszHc8

While processing files with static-html (for target web.browser):
localhost_2017-12-29_16-09-47.report.html:6: Can't set DOCTYPE here. (Meteor sets

The behavior can be seen here: https://youtu.be/T3r1Nu01rgI

The issue is related with: ilan-schemoul/meteor-service-worker#5