If you supply a relative path, it MUST begin with a /. This is either the name of a default Project Icon Image from the list below OR a relative path from the Project Root Folder to the image (JPG or PNG) that should be used as the Project Icon. If you omit this value, it defaults to 0. If 1, renaming the folder has no effect on displayValue. If 0, CodeKit will keep displayValue in sync with the Project Root Folder name (as the user renames the folder, the displayValue will be updated to match). If this is omitted, the name of the Project Root Folder will be used. The name of the Project as it appears in the UI. If you omit this property, CodeKit will set it to whatever date the user first added this Project to the app, which is probably what you want. Stored as the number of seconds since 00:00:00 UTC on 1 January 2001 in Double format. The top level of the Config File is an object of type "creationDate" - Double It is NOT safe to use Number to represent numberical values in this case. If you are reading a Config File, you must treat numbers as 64-bit integers because you do not control whether or not they have bits beyond (2^53) "enabled". For example, fileType can be set to 2 (2^1) to represent a Sass file or 4096 (2^12) to represent a Markdown file. If you are writing a Config File from scratch and the values you intend to store for the properites that MUST be 64-bit integers do not exceed 53 bits of precision, you can safely write the value as a standard Number. It is not officially part of the spec right now. Fortunately, JavaScript is introducing the BigInt type to solve this problem. The Number type stops at 53-bits of precision because JavaScript is a god-awful language. The specific numerical values that MUST be treated as 64-bit integers are called out in this documentation.Īs of 2019, JavaScript cannot represent 64-bit integers natively. This is because several numbers are actually bitmask values. 64-Bit Integers:Ĭertain numbers in the Config File MUST be parsed as 64-bit integers. While this is not a requirement, it is handy for users. To prevent extraneous diffs during Git commits, CodeKit alphabetically sorts all keys in the Config File. All other fields in the Config File are optional. There are only two required fields, both of which are top-level properties: settingsFileVersion and creatorBuild. (The folder added to CodeKit as a Project.) The file must be located in the root Project folder. A CodeKit 3 configuration file stores information about a CodeKit Project, its settings, and all the files it contains.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |