Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ole Henrik Skogstrøm
    @ohenrik
    Thank you. I'll try it. :)
    marocchino
    @marocchino
    :+1:
    Ole Henrik Skogstrøm
    @ohenrik
    So i got this output:
    pick 1119114 Add feature Avatar
    pick 80d8150 Avatar acceps background parametre
    pick f895c13 Correct missing file include
    
    # Rebase 5dfc2ca..f895c13 onto 5dfc2ca
    #
    # Commands:
    #  p, pick = use commit
    #  r, reword = use commit, but edit the commit message
    #  e, edit = use commit, but stop for amending
    #  s, squash = use commit, but meld into previous commit
    #  f, fixup = like "squash", but discard this commit's log message
    #  x, exec = run command (the rest of the line) using shell
    #
    # These lines can be re-ordered; they are executed from top to bottom.
    #
    # If you remove a line here THAT COMMIT WILL BE LOST.
    #
    # However, if you remove everything, the rebase will be aborted.
    #
    # Note that empty commits are commented out
    Should i remove the three first lines and then :wq
    marocchino
    @marocchino
    no. -3-
    Hannes Maack
    @rocknruby
    rename the ‘pick' in line 2 and 3 to squash
    :wq
    “ If you remove a line here THAT COMMIT WILL BE LOST. "
    Ole Henrik Skogstrøm
    @ohenrik
    So like this then:
    pick 1119114 Add feature Avatar
    squash 80d8150 Avatar acceps background parametre
    squash f895c13 Correct missing file include
    
    # Rebase 5dfc2ca..f895c13 onto 5dfc2ca
    #
    # Commands:
    #  p, pick = use commit
    #  r, reword = use commit, but edit the commit message
    #  e, edit = use commit, but stop for amending
    #  s, squash = use commit, but meld into previous commit
    #  f, fixup = like "squash", but discard this commit's log message
    #  x, exec = run command (the rest of the line) using shell
    #
    # These lines can be re-ordered; they are executed from top to bottom.
    #
    # If you remove a line here THAT COMMIT WILL BE LOST.
    #
    # However, if you remove everything, the rebase will be aborted.
    #
    # Note that empty commits are commented out
    Hannes Maack
    @rocknruby
    No
    yeah
    marocchino
    @marocchino
    :clap:
    Ole Henrik Skogstrøm
    @ohenrik
    ;) wrong lines first
    Cool ok, then :)
    Hannes Maack
    @rocknruby
    :cake:
    Hannes Maack
    @rocknruby
    well done
    Ole Henrik Skogstrøm
    @ohenrik
    Perfect :) I'll enjoy the :cake: then :)
    Hannes Maack
    @rocknruby
    @marocchino do have a opinion to #181 ?
    marocchino
    @marocchino
    hmm...
    Is the problem start with 0 number?
    marocchino
    @marocchino
    That is also natural in Japan and Korea.
    Maybe we can make kinda allow_zero_start flag
    marocchino
    @marocchino
    def self.numerify(*masks, allow_zero_start=true)
      loop do
        num = masks.flatten.sample.gsub(/#/) { rand(10).to_s }
        break if allow_zero_start || num[0] != "0"
      end
      num
    end
    Hannes Maack
    @rocknruby
    Yeah, good idea.
    Something like that
    marocchino
    @marocchino
    :smile:
    Rico Sta. Cruz
    @rstacruz
    hey guys. any ffaker maintainers here?
    I am one, and I need FFaker for a project and I see some outstanding issues that can be fixed
    was wondering if anyone can review my changes before pushing them
    marocchino
    @marocchino
    I'm not a maintainer of this repo. But, feel free to open PR
    marocchino
    @marocchino
    Hi, ffaker team. :smile:
    I made a PR. EmmanuelOga/ffaker#200
    please, review it at your free time.
    Rico Sta. Cruz
    @rstacruz
    sup @marocchino
    marocchino
    @marocchino
    yes.
    hi~
    @rstacruz
    Rico Sta. Cruz
    @rstacruz
    ;)
    Matías Gagliano
    @matiasgagliano
    Hi, I hope not to be out of place with this but may I ask why the sudden change of namespace?
    It broke most my tests and it doesn't seem to be something strictly necessary. Tastes aside (I liked "Faker"), I'd guess that those using FFaker wouldn't also use or install Faker, I don't see the conflict there.
    Hannes Maack
    @rocknruby
    I released recently version 2.1.0
    Hannes Maack
    @rocknruby
    @matiasgagliano , its not very common to have two gem`s like faker and ffaker using / sharing the same namespace. The possibility to get a collision while using both gems at the same time was reason enough to create the major release 2.0.0. I guess to upgrade to the version > 2.0.0 is just a search and replace issue, right? - sorry for the late response.
    I released recently version 2.1.0 @/all
    Hannes Maack
    @rocknruby
    @marocchino new year new release? - our last release is almost 6 month ago
    StevenSolomon
    @steven-solomon
    Hey ffaker team, Is there a way to seed word generation with a seed? We want to seed it with our rspec seed.
    Matthew Nielsen
    @xunker
    @steven-solomon I just started working on a branch that does that: ffaker/ffaker#285. It's still a work-in-progress (needs the rest of the modules updated, and integration with rspec/minitest/test-unit random seed), but you're welcome to play with it. I'd love any feedback you have on it.
    marocchino
    @marocchino
    I just merged ffaker/ffaker#285.
    Can anyone release this?
    I do not have release privileges. >_<
    Alex Piechowski
    @pachonk
    Hi there!
    I'm just curious... What makes ffaker "so much better"