linksplatform / linksplatform/Data.Doublets.Json

Change markers to types

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C# help wanted
Dominant language
C#
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Meaning root should be named just Type or RootType.

https://github.com/linksplatform/Data.Doublets.Json/blob/eac0583ca58f992e338352f3e755b4674f479e10/csharp/Platform.Data.Doublets.Json/DefaultJsonStorage.cs#L280-L281

Each marker is just type "inherited" from root type. So, marker links should be like this: (Object: Type -> Object)

https://github.com/linksplatform/Data.Doublets.Json/blob/eac0583ca58f992e338352f3e755b4674f479e10/csharp/Platform.Data.Doublets.Json/DefaultJsonStorage.cs#L284-L296

Each marker can be named just Object or ObjectType instead of "marker".

The basic type system is like this:

Type -> Type
Type -> Value

So everything that comes after Type is Type or Value. Meaning, we can have infinite depth hierarchy of types. The special case of type is a concrete value (constant of some type).

For example, we can have:

(Array: Type -> Array)
(EmptyArray: Array -> EmptyArray)

Meaning that Array is type. And EmptyArray is concrete value (constant) of type Array.

Each value/constant is still type. Each type can be used as a standalone constant.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked sections of csharp/Platform.Data.Doublets.Json/DefaultJsonStorage.cs around lines 280-296. Trace how markers and the root type are represented, then compare the result with the Type, Value, Array, and EmptyArray examples in the issue. Done means the representation follows the proposed type hierarchy and naming consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.