Grunt.js

npm init creates package.json

npm install grunt --save-dev -> is added dependencies to package.json file.

{
  "name": "sample-test",
  "version": "1.0.0",
  "description": "generated for grunt json",
  "main": "Gruntfile.js",
  "dependencies": {},
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "grunt": "^1.0.4"  }
}




npm install grunt-autoprefixer --save-dev


{
  "name": "sample-test",
  "version": "1.0.0",
  "description": "generated for grunt json",
  "main": "Gruntfile.js",
  "dependencies": {},
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "grunt": "^1.0.4",
    "grunt-autoprefixer": "^3.0.4"
  }
}











































Yorumlar











Yorum Gönder































Bu blogdaki popüler yayınlar









SDLC - Software Development Life Cycle




















Resim







SDLC -  Software Development Life Cycle  is a process used by the software industry to design, develop and test high quality softwares.   1- Requirement Analysis  2- Defining Requirements   To clearly define and document the product requirements  SRS (Software Requirement Specification)   document which consists of all the product requirements  to be designed and developed during the project life cycle.    3-   Designing  the Product Architecture    One design approach for the product architecture is proposed and documented in a DDS - Design Document Specification .  DDS  is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product.  DDS  defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules.    4- Developing  the ...








Devamı











@SerializedName and @Expose annotations





















 The  @SerializedName  annotation is needed for Gson to map the JSON keys with our fields. In keeping with Java's camelCase naming convention for class member properties, it is not recommended to use underscores to separate words in a variable.  @SerializedName  helps translate between the two.    @SerializedName ( "quota_remaining" )  @Expose   private  Integer quotaRemaining;    In the example above, we are telling Gson that our JSON key  quota_remaining  should be mapped to the Java field  quotaRemaining .  If both of these values were the same, i.e. if our JSON key was  quotaRemaining  just like the Java field, then there would be no need for the  @SerializedName  annotation on the field because Gson would map them automatically.   The  @Expose  annotation indicates that this member should be exposed for JSON serialization or deserialization.   








Devamı