Most of the blogs are related to ruby and rails developer problems.
Angular 2 basic terminologies
Get link
Facebook
X
Pinterest
Email
Other Apps
-
Transpiler :
A source-to-source compiler, transcompiler or transpiler
is a type of compiler that takes the source code of a program written
in one programming language as its input and produces the equivalent
source code in another programming language.
Decorator :
Decorators are a proposed standard
for ECMAScript 2016 by Yehuda Katz, to annotate and modify classes and
properties at design time. This sounds pretty much like what annotations
do right? Well… sort of. Let’s take a look at what a decorator looks
like:
// A simple decorator@decoratorExpressionclassMyClass{}
Wait. This looks exactly like an AtScript annotation! That’s right.
But it isn’t. From a consumer perspective, a decorator indeed looks like
the thing that we know as “AtScript Annotation”. There is a significant
difference though. We are in charge of what our decorator does to our code. Taking the code above, a corresponding decorator implementation for @decoratorExpression could look like this:
functiondecoratorExpression(target){// Add a property on targettarget.annotated=true;}
Right. A decorator is just a function that gives you access to the target
that needs to be decorated. Get the idea? Instead of having a
transpiler that decides where your annotations go, we are in charge of
defining what a specific decoration/annotation does.
This, of course, also enables us to implement a decorator that adds
metadata to our code the same way AtScript annotations do (I keep
referring to “AtScript annotations” because what they do, is really an
AtScript specific thing). Or in other words: with decorators, we can
build annotations. ===================================================
Some basic files and terminologies which are used in angular 2 application : package.json lists packages the QuickStart app depends on and
defines some useful scripts.
tsconfig.json is the TypeScript compiler configuration file.
I have been searching a lot for this to implement SAML IdP initiated SSO in Rails. Firstly what I found several resources on it for rails they are very few: 1.) ruby-saml gem is to implement Service Provider in SAML. 2.) saml_idp gem is to implementing SAML IdP using but this gem does not provide the way to implement IdP initiated SSO it is for SP initiated SSO. 3.) libsaml which provides the core functionality in SAML IdP but found very hard to implement SAML IdP initiated SSO because @benoist the owner of this gem does not documented it properly even all gems provided for SAML doest not have a proper documentatio. 4.) Another gem is saml_tool which actually provides the way to generate metadata and assertion for SAML request and response. 5.) And Yes, there was a great example for saml idp which saml_tools_demo which describes the use of saml_tools gem. Using Saml_idp and saml_tool gem I finally implemented SAML IdP initiated SSO. And I have described...
Introduction OAuth 2 is an authorization framework that enables applications to obtain limited access to user accounts on an HTTP service, such as Facebook, GitHub, and DigitalOcean. It works by delegating user authentication to the service that hosts the user account, and authorizing third-party applications to access the user account. OAuth 2 provides authorization flows for web and desktop applications, and mobile devices. This informational guide is geared towards application developers, and provides an overview of OAuth 2 roles, authorization grant types, use cases, and flows. Let's get started with OAuth Roles! OAuth Roles OAuth defines four roles: Resource Owner Client Resource Server Authorization Server We will detail each role in the following subsections. Resource Owner: User The resource owner is the user who authorizes an application to access their account. The application's access to the user's account is limited to the...
If you setup a Rails 4 app, you’ll notice the app/models/concerns and app/controllers/concerns directories. Concerns are modules that can be mixed into your models and controllers to share code between them. Some developers falsely classify mixins as composition when they are actually a form of inheritance. When you include a module in a class, that module’s methods are added to the inheritance chain just like a parent class’ methods are added to a subclass. So, don’t think you’ve solved the problem of inheritance by simply splitting your inherited code into separate files! That being said, mixins can be a valuable tool to share code between classes that are otherwise unrelated. Here’s an example of how I chose to use it recently. I have an admin control...
Comments
Post a Comment