Skip to content

Instantly share code, notes, and snippets.

Jaco Joubert jacojoubert

  • Toronto, Canada
Block or report user

Report or block jacojoubert

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
View jsconfig.json
{
"compilerOptions": {
"target": "es6",
"experimentalDecorators": true,
"baseUrl": "."
},
"exclude": [
"dist",
"node_modules",
"temp",
View EmberJS2019.md

As a front-end developer that started our as a designer, building highly polished and accessible UI components that also has a great developer experience is really imporant to me. Ember has been a powerful tool to accomplish this and Octane has made huge improvements to the overall quality of the code.

But, this wouldn't be a Ember 2019 roadmap blog post if there weren't a desire for improvement.

1. Components

When I design a new component I mock up the visual and UX design to make sure it will look good, function well, and be fully accessible. Part of that design process is figuring out the UX for the developer. I like to start with the desired invocation API and work my way backwards to the implementation. However, when you start building really complex interactive components you quickly run into limitations with Ember.

For example, if you were to try to re-implement the native select in Ember with custom <Select> and <Option> components you would quickly run into walls. Take this hypoth

@jacojoubert
jacojoubert / gist:f59d18c229b9a72c032d
Created May 6, 2015
Ember Sample Authentication Service
View gist:f59d18c229b9a72c032d
`import Ember from 'ember'`
`import ajax from 'ic-ajax'`
`import config from 'bonjour-client/config/environment'`
storeProxy = Ember.computed (key, value) ->
key = "bonjour:#{key}"
if arguments.length == 1
window.localStorage.getItem key
else
View gist:77f1da47950f058d061f
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><StringToSignBytes>65 79 4a 6c 65 48 42 70 63 6d 46 30 61 57 39 75 49 6a 6f 69 4d 6a 41 78 4e 43 30 77 4f 43 30 79 4e 46 51 77 4e 7a 6f 78 4e 54 6f 79 4d 69 34 31 4e 7a 6c 61 49 69 77 69 59 32 39 75 5a 47 6c 30 61 57 39 75 63 79 49 36 57 33 73 69 59 6e 56 6a 61 32 56 30 49 6a 6f 69 61 57 31 68 5a 32 56 7a 4c 6d 4a 76 62 6d 70 76 64 58 49 75 61 58 4d 69 66 53 78 37 49 6d 46 6a 62 43 49 36 49 6e 42 31 59 6d 78 70 59 79 31 79 5a 57 46 6b 49 6e 30 73 65 79 4a 6c 65 48 42 70 63 6d 56 7a 49 6a 6f 69 4d 6a 41 78 4e 43 30 77 4f 43 30 79 4e 46 51 77 4e 7a 6f 78 4e 54 6f 79 4d 69 34 31 4e 7a 6c 61 49 6e 30 73 65 79 4a 7a 64 57 4e 6a 5a 58 4e 7a 58 32 46 6a 64 47 6c 76 62 6c 39 7a 64 47 46 30 64 58 4d 69 4f 69 49 79 4d 44 45 69 66 53 78 62 49 6e 4e 30 59 58 4a 30 63 79 31 33 61 58 52 6f 49 69 77 69 4a 47 74 6c 6
View gist:733457
0px;
}
.blog-post .meta {
margin: 5px 0 18px 0;
}
.blog-post .author {
color: #919191;
margin-right: 15px;
}
.blog-post .author img {
You can’t perform that action at this time.