Why has the Angular Source directory for nakama console been deleted?

[MWessam]

I wanted to create a fork of nakama and add some custom dashboard elements into our own nakama console version and right now it's near impossible to work on because all that exists in the console folder is the built console web page.
Looking back at the prs i can see this occured at this pull request #2360
I am not sure if this is intentional?
But it would be great to maybe re add the angular project once more.

[linear]

NK-1676 Why has the Angular Source directory for nakama console been deleted?

[novabyte]

@MWessam You can read more about the new Heroic UI and motivation for the move to Vue on our announcement about the release:

https://heroiclabs.com/blog/announcing-nakama-console-3/

We're very interested to build up features into the Nakama Console, what kind of views did you want to add?

[MWessam]

@novabyte
Oh got it!
I wanted to extend nakama so that we can define custom type schemas with basic crud operations and specifying the required role for each crud operation. This way I can then auto generate a c# class that extends nakama sdk with statically typed methods for all custom data types we might need :)
Rather than having to deal with jsons and parsing and serialization and what not, just making it much easier to plug and play and easier for game designers to work with ^^

And as for Vue, does it have a seperate github repo? because I can't seem to find anything I can work with in the current nakama repo 🥲

[MWessam]

It's a bit of an ambitious undertaking 😅
I wanted to make game api backends simpler. 90% of the api requirements you have are going to be very simple data types and corresponding crud operations and simple api methods as well as sockets. My plan was to have the users define their data types in the dashboard, the source gen will then generate methods for these specific data type operations, and also the ability to add custom api methods that you can define with simple visual scripting :)

[novabyte]

I wanted to extend nakama so that we can define custom type schemas with basic crud operations and specifying the required role for each crud operation. This way I can then auto generate a c# class that extends nakama sdk with statically typed methods for all custom data types we might need :)

@MWessam Thanks for the additional info. We do this kind of code generation with our Hiro game framework:

• The RPCs are described in Protocol Buffers, which you can see here. We use Enum Value Options to extend Protobuf with custom annotations.
• We use the proto Protobuf parser to walk the messages.
• We use Go templates to generate the C# output.

It works exceptionally well even for larger complex codebases.

Rather than having to deal with jsons and parsing and serialization and what not, just making it much easier to plug and play and easier for game designers to work with ^^

This is an ambitious goal but I'm not sure that this kind of tool would fit within the Nakama Console which is aimed to help with player support and game data management. What you plan to create sounds more like a rapid prototyping tool (almost like how visual scripting is sometimes used with projects). I'd suggest you build it as a standalone tool which talks to the Nakama Console API where you need it to do so. The protocol is available here:

https://github.com/heroiclabs/nakama/blob/master/console/console.proto#L78

Hope this helps.