zachanator070 / rpgtools Goto Github PK

Often times .objs do not come with textures, color selection in the game and model view should also be supported

the frontend should be able to use the policies of the current user to determine what access they have instead of relying on boolean values returned by objects like isAdmin, canRead, canWrite

Have an initiative tracker that automatically adds players as they join the game
Can delete, move, edit, add any item in the list

add functionality to move wiki pages to a different parent

This will fix anonymous components from showing up in React Dev tools

We should probably utilize jwt's better to keep track of what the user has access to both on the front end and the back end

The character rotates alright, but the error comes up anyway?

Can't reproduce consistently..

see https://open5e.com/

sections to go:

• spells
• magic items

• Need to find open source models that match the monsters in the 5e data
• Basic hero models would also be nice
• Basic token models (pawn, meeple) would also be a nice to have

This may include introducing some better oop practices as well as some better state management.

• Change background color in game to something that isn't black
• add border around map with a texture

• when you add a model to the game, you can either select a wiki page that has an attached model, or just the model without wiki info
• be able to select a model in game with a popup that displays wiki info
• be able to attach a wiki to a model in game that doesn't have one attached

Currently to create a domain object, factory methods are used. This has been found to be cumbersome and doesn't abstract anything from the actual domain objects. To get rid of this burden of development, these factory methods should be deprecated.

This should have the security context class and the unit of work class inside it.
This class should be used instead of the security context classes in a lot of instances to avoid injecting the repositories everywhere.
This should make the sever support a single db session across one API request.

delete the cover image of any page
delete the map of places

replace the strength, agility, intelligence etc with a arbitrary list of values that can be changed and named

Currently the role application service does not have any integration tests

This mostly applies to switch cases forking logic off of entity types. These should be replaced with calls directly to the entity classes, or use a mapper class that uses DI to find a right class to execute logic.

can't open chat sometimes, particularly when you have something like the game location window open in the bottom right, it covers up the button

This should remove the need to calculate all permissions for each request. Instead each object will have an ACL that will be referenced when making permission checks.

users are logged out after jwt expires even if they are active on the site

this may include bringing over the entity objects to the common folder so that the hooks can specify the type of the state that they return

• Allow shorthand for /roll to type /r
• If no character is put before the d character, assume it is rolling 1 die
• Allow to add rolls and flat modifiers (e.g. /r d20+d4+2d6+4)

This should happen after the server is converted to typescript.

Areas to write tests for:

• World Settings
• Roles
• Server Settings
• Map

allow users to upload an icon to use for a map pin or use one from a list provided by the server

Currently the frontend and server packages use the common package which results in nested '../../../' references. This is ugly and confusing when switching files while developing. These references should instead use namespaces like @rpgtools/packages/common .

if you add a model to a game, then delete that model, the client is instructed to download that model but it doesn't exist

Need to have a product page that showcases basic features and perhaps a video that further describes the product

Takes up to a minute on load

Do not allow a user to delete the last user in role
Do not assign direct permissions to a user when they create a role

Currently most mutation methods return a huge world object that contains ALL the data for the whole site. This is an anti-pattern and shouldn't be changed to return just the data that was mutated. This will require onCompleted callbacks to update the local client cache. This should be easier with apollo v3.

Title

the typescript changes I currently have don't pass the server integration tests I have had previously written

If user assigned permissions are removed, a user will have to select a role when creating entities to seed initial permissions.