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

Fixed example codes #3851

Merged
merged 1 commit into from Jan 6, 2017
Merged

Fixed example codes #3851

merged 1 commit into from Jan 6, 2017

Conversation

maiha
Copy link
Contributor

@maiha maiha commented Jan 6, 2017

Fixed recent inconsistencies where they almost comes from each : Nil.

  • master: Specs 127 (103 successes, 4 failures, 20 pending)
  • This PR: Specs 127 (107 successes, 0 failures, 20 pending)

powered by https://github.com/maiha/crystal-examples

@@ -39,7 +39,7 @@ module HTML
# require "html"
#
# io = IO::Memory.new
# HTML.escape("Crystal & You", io) # => "Crystal & You"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know this breaking change is good. But this is a current spec.

@asterite
Copy link
Member

asterite commented Jan 6, 2017

Nice, thank you!

I think it would make sense to include your tool https://github.com/maiha/comment-spec.cr in the compiler itself. Then we can generate these specs and run them in travis, to make sure they all pass. And also, any project could use that to make sure example code works and is correct. I guess something like crystal tool docspec or similar. Would you be OK with that?

@maiha
Copy link
Contributor Author

maiha commented Jan 6, 2017

@asterite Definitely! It should be checked in PR phase.

@bcardiff
Copy link
Member

bcardiff commented Jan 6, 2017

If we make the playground generate a dump with the values as expr # => value writing these sample will be something fun.

@asterite asterite merged commit 8328757 into crystal-lang:master Jan 6, 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

Successfully merging this pull request may close these issues.

None yet

3 participants