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

Lines in HAML that start with # are skipped #102

Merged
merged 1 commit into from
Oct 22, 2014
Merged

Conversation

golmansax
Copy link
Contributor

In HAML, lines can start with # as that signifies an HTML id, like:

#my-id{ title: t('translation_key') }

This pull request just adds a spec that fails. Would be happy to contribute though if there are any thoughts about how to address this (or whether it should be addressed at all).

@glebm glebm merged commit 595345e into glebm:master Oct 22, 2014
glebm added a commit that referenced this pull request Oct 22, 2014
Quick fix to the regexp until we have a real SEXP scanner
@golmansax
Copy link
Contributor Author

@glebm Thanks for the quick fix!

bartimaeus added a commit to bartimaeus/i18n-tasks that referenced this pull request Dec 1, 2014
* upstream/master: (39 commits)
  Tidy up the spec template indentation, use let(:unused_keys).
  Update README.md
  Added Gitter badge
  minor fix ignore_lines pattern
  travis: 2.1.1 -> 2.1.3
  .travis latest jruby
  Bump to 0.7.8
  Google Translate fixnum spec glebm#100
  Improve ignore_lines glebm#96 glebm#102
  initialize @key_filter glebm#101
  Lines in HAML that start with # are skipped
  ignore config: better examples
  ru copy fix
  move error message to i18n
  YARD signatures for GoogleTranslation methods
  Possible fix for glebm#99
  README: small fixes for defining custom commands
  Remove unused keys
  fix typo in gemspec [ci skip]
  Simplify commands DSL i18n
  ...

Conflicts:
	spec/google_translate_spec.rb
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

Successfully merging this pull request may close these issues.

2 participants