This repository has been archived by the owner on Dec 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 84
Locking down schema in production mode #93
Milestone
Comments
cheungpat
added a commit
to cheungpat/skygear-server
that referenced
this issue
Jul 28, 2016
Requests authenticated with master key can temporarily override this restriction. refs SkygearIO#93
cheungpat
added a commit
to cheungpat/skygear-server
that referenced
this issue
Aug 1, 2016
Requests authenticated with master key can temporarily override this restriction. refs SkygearIO#93
cheungpat
added a commit
to cheungpat/skygear-server
that referenced
this issue
Aug 1, 2016
Requests authenticated with master key can temporarily override this restriction. refs SkygearIO#93
cheungpat
added a commit
to cheungpat/skygear-server
that referenced
this issue
Aug 1, 2016
Requests authenticated with master key can temporarily override this restriction. refs SkygearIO#93
cheungpat
added a commit
to cheungpat/skygear-doc
that referenced
this issue
Aug 1, 2016
rickmak
added a commit
that referenced
this issue
Aug 1, 2016
bensonby
pushed a commit
to SkygearIO/skygear-doc
that referenced
this issue
Aug 3, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In
record:save
, the schema is automatically extended when there is a new field. This issue should lock down the schema when in production mode (i.e.dev-mode = NO
)The text was updated successfully, but these errors were encountered: