These are chat archives for dcsan/gitterbot

5th
Aug 2015
Jorge Almeida
@Jorgixhallo
Aug 05 2015 00:04
wiki filter
CamperBot
@camperbot
Aug 05 2015 00:04

:pencil: js filter [edit]

The filter() method creates a new array with all elements that pass the test implemented by the provided function

arr.filter(callback[, thisArg])
Parameter
Required Arr
Required callback (function with max 3 args)
Optional thisArg

Return: A new array that contains all the values for which the callback function returns true. If the callback function returns false for all elements of array1, the length of the new array is 0.

MDN link | MSDN link

:pencil: read more about js filter on the FCC Wiki

Jorge Almeida
@Jorgixhallo
Aug 05 2015 00:04
check it inside. I included some examples right?
wouldn't the bot be able to pick them up?
@dcsan
it's the same method you use with the spoiler i gess
dc
@dcsan
Aug 05 2015 00:20
oh ok
wiki filter
CamperBot
@camperbot
Aug 05 2015 00:20

:pencil: js filter [edit]

The filter() method creates a new array with all elements that pass the test implemented by the provided function

arr.filter(callback[, thisArg])
Parameter
Required Arr
Required callback (function with max 3 args)
Optional thisArg

Return: A new array that contains all the values for which the callback function returns true. If the callback function returns false for all elements of array1, the length of the new array is 0.

MDN link | MSDN link

:pencil: read more about js filter on the FCC Wiki

dc
@dcsan
Aug 05 2015 00:21
so the syntax would be like
wiki filter examples ?
CamperBot
@camperbot
Aug 05 2015 00:21
no wiki entry for: filter examples
:pencil: click here to create one now!after creating your page type update to reload it here
dc
@dcsan
Aug 05 2015 00:21
or maybe examples filter ?
then we don't have to deal with people who want to search for two words things eg
  • wiki js loops
example loops
would find that for anything under an 'examples' heading in the wiki?
interesting idea
using the wiki as more structured data
Jorge Almeida
@Jorgixhallo
Aug 05 2015 00:29
yes
dc
@dcsan
Aug 05 2015 00:41
@irinatag did you close this issue?
but you're still reviewing and going to merge?
merged! looks good :)
i need to fix some other stuff and deploy
Jorge Almeida
@Jorgixhallo
Aug 05 2015 01:14
thanks @Jorgixhallo
CamperBot
@camperbot
Aug 05 2015 01:14
jorgixhallo sends brownie points to @jorgixhallo :sparkles: :thumbsup: :sparkles:
:warning: could not find receiver for jorgixhallo
dc
@dcsan
Aug 05 2015 01:21
get em while you can @Jorgixhallo - but you need to creaet an account on beta.fcc
Jorge Almeida
@Jorgixhallo
Aug 05 2015 01:22
is it necessary, or it will merge after the update?
dc
@dcsan
Aug 05 2015 01:23
explain beta
CamperBot
@camperbot
Aug 05 2015 01:23

:pencil: beta [edit]

What happens in betas, stays in betas

The beta release is where we ask people to test out new features.

Your progress on beta.freecodecamp.com will NOT be saved to freecodecamp.com's database!

We really appreciate everyone's help ironing out our Beta Release, but please understand that it's not possible to merge two user databases with completely different sets of content. Think of our beta as just a preview test, to check things work properly. In fact the database maybe reset at any time so we can try out things like the sign-up process.

Feel free to experiment with our beta site, but note the following:

  • Our beta site is quite buggy. If you notice a bug, please make sure it's a new one before you create an issue.
  • We've removed all authentication options other than GitHub from our beta. Don't worry - you will still be able to sign in using LinkedIn, Twitter, Google and Facebook in the future.
  • Our beta database is an old version of Free Code Camp's database. Your Free Code Camp account may not yet exist on the beta site, so please create one if you want to experiment with it.

Also, please remember that all our Waypoint challenges are optional. You will not have to go back and complete new waypoints as we add them.

We plan to merge all these new beta features into freecodecamp.com as soon as we've worked out all the major bugs.
:pencil: read more about beta on the FCC Wiki

Jorge Almeida
@Jorgixhallo
Aug 05 2015 01:24
I'll make it tomorrow anyway
how to pass a bonfire:
function sumAll(arr) {
  if(Math.random(1)>0.5){
    return 10;
  } else {
    return 45;
  }
}

sumAll([1, 4]);
with enough clicks you can make it easilly. took me like 20/30
some hiden (but very easy) tests could prevent this maybe
@dcsan @BerkeleyTrue
M Used
@mildused
Aug 05 2015 06:57
Hi Hi HI
dc
@dcsan
Aug 05 2015 07:13
HALO
M Used
@mildused
Aug 05 2015 07:15
@dcsan Where could I learn the necessary background to work on this gitter bot?
dc
@dcsan
Aug 05 2015 07:15
right here :)
if you know JS/node, you can get started
M Used
@mildused
Aug 05 2015 07:16
ahh, I'm still on ziplines
dc
@dcsan
Aug 05 2015 07:16
you don't have to understand the whole system - you could create a new botCommand with just basic JS
well it looks like you've done tons of JS stuff
are you on win or *nix ?
M Used
@mildused
Aug 05 2015 07:17
win
dc
@dcsan
Aug 05 2015 07:17
ok well it runs almostly instantly on windows
Bill
@kirah1314
Aug 05 2015 07:17
@dcsan ok
dc
@dcsan
Aug 05 2015 07:17
if you get node/iojs running
M Used
@mildused
Aug 05 2015 07:17
@dcsan ok
Abhisek Pattnaik
@abhisekp
Aug 05 2015 07:17
@dcsan did you fix the ES6 backticks to work on node ?
dc
@dcsan
Aug 05 2015 07:17
@benmcmahon100 is also on Windows
if you're running iojs thats not a problem
but i do have a ticket for that
dcsan/gitterbot#60
you're worried about updating to iojs ?
you have to make the jump into server land sometime!
Abhisek Pattnaik
@abhisekp
Aug 05 2015 07:20
yeah! So we conclude... :P
dc
@dcsan
Aug 05 2015 07:21
OK i can try and get it running on just vanilla node tomorrow if you're gonna help with some stuff
:diamonds: deal?
i just tried running on node and got one more error
if (!name.includes(".md")) {
various bits of ES6 code i've used around
Abhisek Pattnaik
@abhisekp
Aug 05 2015 07:25
:-1: no deal. Well, not for now. :(
dc
@dcsan
Aug 05 2015 07:25
thats with --harmony
Abhisek Pattnaik
@abhisekp
Aug 05 2015 07:26
@dcsan you can check the difference of node --harmony and IOjs and correct the relevant parts.
http://kangax.github.io/compat-table/es6/#iojs
dc
@dcsan
Aug 05 2015 07:29
will check tmrw
Bill
@kirah1314
Aug 05 2015 08:25
@dcsan I'm gonna do the hint for bonfire reverse a string. Is there a specific format we should follow and should I put the working codes on the hint page too? I read the Wiki Style Guide, should I just follow this?
Ben McMahon
@benmcmahon100
Aug 05 2015 09:35
@abhisekp are you on webstorm?
Abhisek Pattnaik
@abhisekp
Aug 05 2015 09:36
@benmcmahon100 I've Webstorm but it runs slow so not yet installed. I use Brackets [ ] currently.
Ben McMahon
@benmcmahon100
Aug 05 2015 09:40
Okay one sec I'll check my configs
Jorge Almeida
@Jorgixhallo
Aug 05 2015 09:51
wiki style
CamperBot
@camperbot
Aug 05 2015 09:51

:point_right: bonfire style guide [wiki]

work in progress

Bonfire Style Guide

Writing Bonfire challenges is a great way to exercise your own problem solving and testing abilities. It is a simple three step process.

  1. Fill out the generator form and test your challenge: http://www.freecodecamp.com/bonfire-challenge-generator
  2. Once you have confirmed a working bonfire challenge in the generator, copy and paste the the fields into the JSON generator: http://www.freecodecamp.com/bonfire-json-generator
  3. Copy the JSON, fork the freecodecamp repository, and submit a pull request with your addition to the bonfires.json: https://github.com/FreeCodeCamp/freecodecamp/blob/master/seed_data/bonfires.json

:pencil: read more about bonfire style guide on the FCC Wiki

dc
@dcsan
Aug 05 2015 09:52
@kirah1314 just add a h2 heading for each hint to separate them. Tippy can add Medora or anything else you like.
Ben McMahon
@benmcmahon100
Aug 05 2015 09:58
@abhisekp iojs -- harmony app
or iojs app -- harmony
Jorge Almeida
@Jorgixhallo
Aug 05 2015 10:03
@dcsan maybe the references should come before the solution? at least people could have a chance to read them if they really want to. Because references can be different from the link that are in the problem right?
that could lead them to an answer
Abhisek Pattnaik
@abhisekp
Aug 05 2015 10:16
@benmcmahon100 iojs doesn't need the flag. It has ES6 built in. NodeJS need --harmony flag.
Ben McMahon
@benmcmahon100
Aug 05 2015 10:16
I had to use harmony to get it to work
Are you still getting a flag on include?
Abhisek Pattnaik
@abhisekp
Aug 05 2015 10:18
@benmcmahon100 please ask @dcsan
But @dcsan must be sleeping now. :sleeping:
Ask him after 6 hrs. :sparkles:
Ben McMahon
@benmcmahon100
Aug 05 2015 10:18
@abhisekp I'm asking you though :p
Does your environment work?
Abhisek Pattnaik
@abhisekp
Aug 05 2015 10:19
@benmcmahon100 haven't used it. So no idea. I'm going to now, in C9.io
Ben McMahon
@benmcmahon100
Aug 05 2015 10:20
c9? It should work locally but what ever suits! It does work on windows but you definitely need iojs and mine still wasn't happy until i added harmony
Lightwaves
@Lightwaves
Aug 05 2015 14:50
dc you have them fighting over browny points haha
Abhisek Pattnaik
@abhisekp
Aug 05 2015 15:48
thanks @Lightwaves
CamperBot
@camperbot
Aug 05 2015 15:48
abhisekp sends brownie points to @lightwaves :sparkles: :thumbsup: :sparkles:
:star: 129 | @lightwaves | http://www.freecodecamp.com/lightwaves
Bill
@kirah1314
Aug 05 2015 19:51
@dcsan you there?
dc
@dcsan
Aug 05 2015 20:41
hi @kirah1314
Bill
@kirah1314
Aug 05 2015 20:58
@dcsan i sent you a pm, just wondering if you could check the wiki for reverse a string and let me know if that's a good format to use. I just finished it at first :)
Abhisek Pattnaik
@abhisekp
Aug 05 2015 21:00
bf reverse
CamperBot
@camperbot
Aug 05 2015 21:00

:fire:Bonfire: Reverse a String :link:

function reverseString(str) {
  return str;
}

reverseString('hello');

Reverse the provided string.
You may need to turn the string into an array before you can reverse it.
Your result must be a string.
Remember to use RSAP if you get stuck. Try to pair program. Write your own code.

type: bf details bf links bf spoiler

dc
@dcsan
Aug 05 2015 21:08
find reverse
CamperBot
@camperbot
Aug 05 2015 21:08

find reverse

[0] bonfire: reverse a string

dc
@dcsan
Aug 05 2015 21:09
hmm i think the colon in the name may have screwed things up
update
CamperBot
@camperbot
Aug 05 2015 21:09
updating wiki...
Updating 2fbef9e..f35b55a Fast-forward
Bonfire:-Reverse-a-String.md => Bonfire-Reverse-a-String.md | 12 ++++++++++-- js-filter.md | 2 ++ 2 files changed, 12 insertions(+), 2 deletions(-) rename Bonfire:-Reverse-a-String.md => Bonfire-Reverse-a-String.md (72%)
done code: 0
:computer:
dc
@dcsan
Aug 05 2015 21:09
help reverse
CamperBot
@camperbot
Aug 05 2015 21:09

:point_right: bonfire reverse a string [wiki]

Summary

For this bonfire our goal is to reverse the provided string. There are 4 green checks (objectives) our code needs to pass in order to complete this bonfire:

  1. The final object is expected to be a string
  2. "hello" is expected to be "olleh"
  3. "Howdy" is expected to be "ydowH"
  4. "Greetings from Earth" is expected to be "htraE morf sgniteerG"

:pencil: read more about bonfire reverse a string on the FCC Wiki

dc
@dcsan
Aug 05 2015 21:09
bf reverse
CamperBot
@camperbot
Aug 05 2015 21:09

:fire:Bonfire: Reverse a String :link:

function reverseString(str) {
  return str;
}

reverseString('hello');

Reverse the provided string.
You may need to turn the string into an array before you can reverse it.
Your result must be a string.
Remember to use RSAP if you get stuck. Try to pair program. Write your own code.

type: bf details bf links bf spoiler

dc
@dcsan
Aug 05 2015 21:10
bf spoiler
CamperBot
@camperbot
Aug 05 2015 21:10
:construction: Spoilers are only in the Bonfire's Custom Room :point_right:
dc
@dcsan
Aug 05 2015 21:11
update
CamperBot
@camperbot
Aug 05 2015 21:11
updating wiki...
Updating f35b55a..acbeae9 Fast-forward
Bonfire-Reverse-a-String.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
done code: 0
:computer:
dc
@dcsan
Aug 05 2015 21:12
hey @kirah1314 looks cool i checked it out
couple things

filenames

should not have any punctuation in

next hint

you don't really need to put that in the wiki article itself
users can page through and just type "hint" each time to get next
Bill
@kirah1314
Aug 05 2015 21:12
so just have it all under 1 page?
dc
@dcsan
Aug 05 2015 21:12
in the BF's special room
check it out
Bill
@kirah1314
Aug 05 2015 21:13
ah ok
go there and type hint
hint
CamperBot
@camperbot
Aug 05 2015 21:13
:construction: Spoilers are only in the Bonfire's Custom Room :point_right:
M Used
@mildused
Aug 05 2015 22:54
Gitter bot assumes my user on FCC is the same as my user on Github? Or am I wrong?
Lightwaves
@Lightwaves
Aug 05 2015 23:10
@dcsan for the reverse a string bonfire there is an alternative solution besides the split reverse (although I did use the split reverse solution)
you can build the string by iterating backwards
dc
@dcsan
Aug 05 2015 23:53
ok...
maybe you can add that to the wiki page?
we have a wiki hint for that now
thanks to @kirah1314 ^ @Lightwaves
CamperBot
@camperbot
Aug 05 2015 23:53
dcsan sends brownie points to @kirah1314 and @lightwaves :sparkles: :thumbsup: :sparkles:
:star: 130 | @lightwaves | http://www.freecodecamp.com/lightwaves
:star: 92 | @kirah1314 | http://www.freecodecamp.com/kirah1314
dc
@dcsan
Aug 05 2015 23:53
@mildused thats correct
you can change your FCC name
also its on the beta site for now