rojo-rbx/rojo
1
0
Fork 1
mirror of https://github.com/rojo-rbx/rojo.git synced 2026-04-26 07:36:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update docs to talk about default.project.json

Browse Source
This commit is contained in:
Lucien Greathouse
2019-02-01 18:03:41 -08:00
parent 69d1accf3f
commit 2c2554d73d
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/getting-started/creating-a-place.md
View File

@@ -9,7 +9,7 @@ cd my-new-project
rojo init rojo init
``` ```
Rojo will make a small project file in your directory, named `roblox-project.json`. It'll make sure that any code in the directory `src` will get put into `ReplicatedStorage.Source`. Rojo will make a small project file in your directory, named `default.project.json`. It'll make sure that any code in the directory `src` will get put into `ReplicatedStorage.Source`.
Speaking of, let's make sure we create a directory named `src`, and maybe a Lua file inside of it: Speaking of, let's make sure we create a directory named `src`, and maybe a Lua file inside of it:

2
docs/migrating-to-epiphany.md
View File

@@ -1,7 +1,7 @@
Rojo underwent a large refactor during most of 2018 to enable a bunch of new features and lay groundwork for lots more in 2019. As such, Rojo **0.5.x** projects are not compatible with Rojo **0.4.x** projects. Rojo underwent a large refactor during most of 2018 to enable a bunch of new features and lay groundwork for lots more in 2019. As such, Rojo **0.5.x** projects are not compatible with Rojo **0.4.x** projects.
## Supporting Both 0.4.x and 0.5.x ## Supporting Both 0.4.x and 0.5.x
Rojo 0.5.x uses a different name for its project format. While 0.4.x used `rojo.json`, 0.5.x uses `roblox-project.json`, which allows them to coexist. Rojo 0.5.x uses a different name for its project format. While 0.4.x used `rojo.json`, 0.5.x uses `default.project.json`, which allows them to coexist.
If you aren't sure about upgrading or want to upgrade gradually, it's possible to keep both files in the same project without causing problems. If you aren't sure about upgrading or want to upgrade gradually, it's possible to keep both files in the same project without causing problems.