This relates to #6. I don't know if it really solves this issue, but reading the discussion it seemed like a good tradeoff between keeping the design and adding a playground element.
Hope this helps, if you need any changes just ping me 👍
(Embedding doesn't work due to https://github.com/rex...
This PR allows us to get the source code of espressos APIs (which are not checked in to this project) and generate code from them. The generated file is just for display and not used yet, this would be the next step 👍
I just noticed that the docs had broken images, possibly through the renaming in the organisation.
I hope I followed the contributing guidelines correctly, if not please let me know 👍
Happy Holidays ❄️
Just wanted to share this with you, tested out how to add a jest test runner for go and how it performs, here are the results:
- Current: 8.27s total execution time
- Jest Runner: 163.44s total execution time
So, yeah, you were right 🤷♂️
I like your project very much and I thought it could benefit from having automated code formatting, so I added prettier. It is executed in a pre-commit hook, so it should make the code here consistent 👍
First of all, thanks for this great project 👍
Docker now supports [multi-staged builds](https://docs.docker.com/engine/userguide/eng-image/multistage-build/) which allows us not use two images manually but have all the build process in one image. I thought this might help, if you...
as mentioned in #61 this is my try to add automated releases to this project.
Only thing needed is to check in a Github token and npm email and token (and activate in travis) then it should work. You can then git-tag a version and it will automatically be build and uploaded to your ...
I like your project very much and I would like to enable people with no node installed to use it, so I included a packaging step. The build binaries are included in the `packed/` folder. You can upload them in your releases (working on automating this too, if you'd like to)
First of all thanks for your great library, it was a real time saver for me!
I just happened to find that the README was a bit outdated with missing `react-native link` mention for the installation and the wrong imports.
If you need any further adjustments, please let me know.
Just a small change, but as far as I can see jQuery is not included by default, so it's not out of the box in the generated app.
No big deal, but I wondered for a second, so I wanted to let you know ;)
Have a nice day!
We needed this feature in our application, so I thought it might be a nice thing to have it also here at the original component. Feel free to revert the example changes if they don't seem appropriate to you.
One may wonder where dismissKeyboard comes from, it is defined [here](htt...
I just gave the problem #14 and #19 a try. Somehow the previously merged commits are shown in the diff too, although they should be in master here already, I don't know why. Anyways:
What I did:
- added build script using babel and used it as prepublish script
- checked in th...
This PR should fix #6 :+1:
Unfortunately I am not sure how to reproduce the bug mentioned in b9008691ea614af238296λ278674659a73645c7 by @brentvatne, would one be so kind to check if my implementation works with this usecase?
The `pointerEvents="none"` also killed the pointer e...
Also added the latest compiled source, keyboard handling was missing due to merge conflicts.
This should fix the bug with the latest spec of the component and also keep existing iOS only users happy, as it won't change a thing to them.
The react native packager changed its behavior, so that simlpy requiring it won't work
Instead we use the relative path now, we should occasionally check if the global require will work again, as this may break on restructuring
Additionally had to add autobind-decorators back, as we still use...
So, one last PR, but I thought this makes sense for most open source projects, so why not add it here.
[EditorConfig](http://editorconfig.org/) is an awesome projects, which enables future contributors to easily have the right settings in their editor in order to keep the basic code style for...
First of all, thanks for this great component, it was really easy to use it and did exactly what I expected, nice work! The only problem I had was the changes of the statusbar, which where not mentioned and (to my mind) unnecessary. One could easily add this behavior by adding a onDr...
I fixed all eshint errors and commented some code out (in brim.js line 48-63) which may be deleted, I think.
#6 would have to be merged before this one, as this one combines both PRs.
Have a nice day ;)
First of all, thanks for this great library! I thought you may use some help, so I did the changes you purposed in #5 . I am looking further to fix the linting errors ;)
Unfortunately I had to remove some options as they are only supported in eslint > 0.10.0 and gulp-eslint seems to use a low...