diff --git a/tr/overview.md b/tr/overview.md index 5a4bfd811e0f6eb2baf4008a2edaacf36e95a698..63f84d268fdca1c78e56dd64df9612756b853828 100644 --- a/tr/overview.md +++ b/tr/overview.md @@ -1,4 +1,4 @@ -The Ferma schema is defined by a collection of interfaces and classes written by the user. Each method will interact with the underlying graph to either modify the graph in some way, or to retrieve an element or property from the graph. There are two techniques for defining how these methods behave. Either you can explicitly implement the method, or you can leave the method as abstract and annotate the method in order to allow Ferma to implement the method for you. Here we will define the annotations available to you and how they work, along with a few examples. +Ferma şeması, kullanıcı tarafından yazılan arayüzlerin ve sınıfların bir koleksiyonuyla tanımlanır. Each method will interact with the underlying graph to either modify the graph in some way, or to retrieve an element or property from the graph. Bu yöntemlerin nasıl davrandığını tanımlamak için iki teknik vardır. Either you can explicitly implement the method, or you can leave the method as abstract and annotate the method in order to allow Ferma to implement the method for you. Here we will define the annotations available to you and how they work, along with a few examples. The behavior of an annotated method is dictated not only by the annotation applied to it but also the method's signature. Therefore an annotated method will behave differently if it's return type, arguments, or even if the method name were to change. It is important to note that when a method is explicitly defined (doesnt use an annotation) then the method signature can be anything.