ap_bunchanumbers

hi hsluoyz, I started with some bugs here - https://github.com/casdoor/casdoor-java-sdk/issues/121

i just got as far as cloning the repo and realizing that i would like some better dx for frontend before i even begin - probably soon i will try to identify the group thing that i came to fix

checking...

sent dm

actually there were frontend changes :)

i think we have contributed before, just not myself (and im pretty sure not frontend)

sure, if it is an open question i can help investigate like create a branch on my fork with some exploring migration paths

I think the DX (developer experience) of working on the frontend can be improved a lot - i recently created https://github.com/casdoor/casdoor/discussions/4486 about the timing of the frontend build but the real motivation is to make a "red carpet" for working on the frontend itself

this speaks also to increasing the quantity and quality of future frontend contributions

we are trying to use casdoor at our company and we are finding all sorts of bugs (frontend and backend) - i wont pollute this channel with the bug reports but one of the bugs we found recently was at least a frontend bug (probably also a backend bug - our backend go guy literally re-implemented the logic from a casdoor endpoint in one of our backend endpoints because using casdoor frontend you can work around the constraint) - so i cloned down casdoor and tried to see if i can get it running.... immediately had to google craco - started wondering why not vite