Inbeom Hwang
Inbeom Hwang
@jashmenn I think we'd better to merge my fork first, as this PR is based on that and all tests pass on it. You can take a look on https://github.com/inbeom/activeuuid....
@aren55555 You might want to try [my fork](https://github.com/inbeom/activeuuid). It passes the tests with Rails 5 environment.
@jashmenn #85, what this one is based on, passes tests on the all environments but the obsolete ones. Can you consider merging it first? I think now almost no one...
@jashmenn Thanks. I will catch up some open issues and prepare to put my hands on the maintenance of this gem.
@rafaelsales I started maintaining my fork of activeuuid https://github.com/inbeom/activeuuid If you're interested, use my fork instead. Thanks!
@tony-currentuser @Confusion Would you try using PR #85 instead? It does patch applications immediately after connections are established, so the load order won't be the problem.
@jloosfelt @kyledecot, how about using [my fork](https://github.com/inbeom/capistrano-unicorn/tree/capistrano3)? I've run it without errors on my environment. https://github.com/inbeom/capistrano-unicorn/tree/capistrano3
엇? ㅋㅋㅋ 두 번 빌드는 생각못했는데 괜찮은 방향같군요. All-or-nothing으로 보면 무서웠는데, 도전해봄직합니다!!
아아.. 곤란하군요 ㅋㅋㅋㅠ 빌드시엔 문제 없지만 플젝에 얹을 때가 이슈이면 한 번에 찾아내기도 쉽진 않을 것 같고.. 조금이라도 쉬워질 길이 있을지 생각해보겠습니다!
전 1안이 좋아 보입니다! SSR할 때 마크업의 크기가 상당히 커서 팝업이나 액션시트 등 최초에 보이지 않는 컴포넌트들은 필요할 때 import하는 게 첫 렌더링 시간을 절약하는 길인 것 같아요.