API Base #2
Labels
No labels
Compat
Breaking
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Meta
Kind
Renovate
Kind
Repository
Kind
Security
Kind
Testing
Kind
Tooling
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Out of Scope
Reviewed
Won't Fix
Size
L
Size
M
Size
S
Size
XL
Size
XS
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Depends on
#6 Add initial src
cswimr/LookingGlass
#11 Set up data models
cswimr/LookingGlass
#12 Authentication
cswimr/LookingGlass
#13 Permissions
cswimr/LookingGlass
Reference: cswimr/LookingGlass#2
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The bare minimum to get me started would be the following:
Need:
Want:
an example of the data being stored would look like this:
@MYHM wrote in https://www.coastalcommits.com/cswimr/myhm-commission/issues/2#issue-286:
What exactly do you mean by this? Do you just mean it should be easy to add new features, i.e. new api endpoints?
Edit: This is also a bit misleading, as while I might find it easy to extend this software, someone else with less C# experience might find it pretty difficult. I'll do my best to document the codebase, but C# knowledge is simply required to contribute.
So realistically this is going to be a you project, unless you absolutely aren't able to do whatever it is I come up with I will always commission you on this, when I first came up with this idea the plan was to make it so I could easily add endpoints without the need of another developer to actually come and do it for me, realistically that is a lot of work for not a lot of payoff. So you can probably just ignore that part if I'm being honest.
Alright, in that case, I'll still document everything, but it shouldn't really be that hard to add new endpoints once the first few are made. EntityFrameworkCore (EFCore), the main C# ORM, is pretty easy to use, so adding endpoints might not necessarily require me if you're willing to give it a shot. I'd be happy to review PRs without a commission