Note: I had issues with setting up my Facebook app so authentication would work. I'd receive the error at the bottom, and it took me a while to figure out what was wrong
Here are the steps I took:
http://developers.facebook.com/, create, and setup your apphttp://localhost:3000/ as "Site URL" (and "Mobile URL" if necessary)localhost to "App Domains" above
First of all you need to decide who will be your target consumers based on the following:
They have the same environment(webpack config, babel config) setup as you where you built your design system(this is mostly possible if you use monorepos/same configs where all the teams share the same environment).
They don't have the same environment which is the case when you work in bigger teams and you want to distribute your design system as any other npm package which is already built and can be used directly.
If your use case falls under case no. 1 then you can just compile the source babel src -d build and leave the bundling to the consumer projects tools(webpack/rollup)
| Git clone com específico branch: | |
| $ git clone --branch <branchname> <remote-repo-url> | |
| Remover todos os commits | |
| $ git checkout --orphan latest_branch | |
| $ git add -A | |
| $ git commit -am "mensagem" | |
| $ git branch -D main | |
| $ git branch -m main | |
| $ git push -f origin main |
| Xcode 11+ | |
| The simplest way using autolayout: | |
| 1. Add UIScrollView and pin it 0,0,0,0 to superview (or your desired size) | |
| 2. Add UIView in ScrollView, pin it 0,0,0,0 to all 4 sides and center it horizontally and vertically. | |
| 3 .In size inspector, change bottom and align center Y priority to 250. (for horizontal scroll change trailing and align center X) | |
| 4. Add all views that you need into this view. Don't forget to set the bottom constraint on the lowest view. | |
| 5. Select the UIScrollView, select the size inspector and deselect Content Layout Guides. |
| $.formUtils.addValidator({ | |
| name : 'cnpj', | |
| validatorFunction : function(value, $el, config, language, $form) { | |
| value = value.replace(/[^\d]+/g,''); | |
| if(value == '') return false; | |
| if (value.length != 14) | |
| return false; | |
| // SWIFT 3 | |
| import UIKit | |
| import Photos | |
| extension PHPhotoLibrary { | |
| // MARK: - PHPhotoLibrary+SaveImage | |
| // MARK: - Public | |
| func savePhoto(image:UIImage, albumName:String, completion:((PHAsset?)->())? = nil) { |
On my dual-drive MacBook Pro I have remapped the eject key to F13 using Karabiner and NoEjectDelay. The eject key has been assigned as the hotkey for a guake-style visor terminal using iTerm2. Having its own hotkey precludes the need for an icon, so I prefer to hide the iTerm dock icon.
####To hide the dock icon of iTerm2 on Mac OS X:
/usr/libexec/PlistBuddy -c 'Add :LSUIElement bool true' /Applications/iTerm.app/Contents/Info.plist####To undo the above:
An application I'm working on has two different types of Devise users, but I want both types of users to be able to use the same sign in form. Devise doesn't make this easy.
You could argue that I really should have a single user type with a role attribute, but the app is far enough along that I don't want to change that early design decision. It could be changed later if more pain points are discovered.
You could also argue that I shouldn't use Devise, but it's still the de facto authentication standard for Rails applications.
In this example, you can sign in as either a User or an AdminUser. This application only has two types of user, but this example could be extended to support any number of them more gracefully.
