Skip to content
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

Whatsapp demo missing step #1498

Closed
9 tasks
andrewcharnley opened this issue Nov 19, 2016 · 1 comment
Closed
9 tasks

Whatsapp demo missing step #1498

andrewcharnley opened this issue Nov 19, 2016 · 1 comment

Comments

@andrewcharnley
Copy link

andrewcharnley commented Nov 19, 2016

Missing:

  1. https://github.com/meteoric/ionic-sass
  2. meteor add meteoric:ionicons-sass --save
  3. app.scss

On the second page of the guide there is a screenshot showing the basic look with the sass applied, but the dependencies (1) and (2) and the file (3) containing the code below has not been done yet.

@import '../../../.meteor/local/build/programs/server/assets/packages/meteoric_ionic-sass/ionic';
@import '../../../.meteor/local/build/programs/server/assets/packages/meteoric_ionicons-sass/ionicons';

Which resolved it (as a new user I'd have given up at this point).

A.

Remember, an issue is not the place to ask questions. You can use Stack Overflow for that, or you may want to start a discussion on the Meteor forum.

Before you open an issue, please check if a similar issue already exists or has been closed before.

When reporting a bug, please be sure to include the following:

  • A descriptive title
  • An isolated way to reproduce the behavior (example: GitHub repository with code isolated to the issue that anyone can clone to observe the problem)
  • What version of angular-meteor you're using, and the platform(s) you're running it on
  • What packages or other dependencies you're using
  • The behavior you expect to see, and the actual behavior

See here for more detail on what is expected of a bug report.

When you open an issue for a feature request, please add as much detail as possible:

  • A descriptive title
  • A description of the problem you're trying to solve, including why you think this is a problem
  • An overview of the suggested solution
  • If the feature changes current behavior, reasons why your solution is better

See here for more detail on what is expected of a feature request.

@Urigo
Copy link
Owner

Urigo commented Oct 31, 2017

Closing due to inactivity and a lot of updates to the tutorial since then.
Please reopen if you are still encountering it

@Urigo Urigo closed this as completed Oct 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants