A new Config section called api will be created.

EVERY REST endpoint will be individually assign permissions from the config file
Example:

{
	"api": {
		"accounts": {
			"create": ["student", "teacher", "admin", "dev"], //Usergroups
			"archive": ["admin", "dev"]
		},
		"passes": {
			"create": ["student", "dev"],
			"cancel": ["student", "teacher", "dev"]
		}
	}
}

you could also split it up and be more specific.
Remember: return will stop all further instructions from executing, so no need to nest if statements.

sorry octocat... The fox has better features and isn't greedy.

@gmeriano You will need a GitLab Account
Once you get that, email me, and I will add you to the contributors.

A read only mirror can be found here

• Add Create Function

• Add Get Function

• Add List Function

  • Support RRule checks in filter
  • Support filtering non RRule blackouts
  • Filter by date time range and get blackouts set for periods that fall in the range and vice versa

• Add Edit Function

• Add Delete Function

• Blackouts should block pass creation

  • Backend
  • Frontend

• Cancel Existing passes and send an email with the blackout reason.
  FUTURE:

• Link into the (uncreated) bulk api system to auto cancel passes

• Link Blackout reason to pass messages and the cancel message

Using passportjs

like google

make it work in passport.js

When the create account function is called quickly in a short amount of time, some emails may bypass the dupe check.

https://sentry.io/joseph-hassell/passport-live-sths/issues/307310183/

ReqlDriverCompileError: Object field 'groupFields' may not be undefined
  File "/home/joseph/Documents/Code/GitKraken/Passport-Live/modules/passport-api/index.js", line 88, in null.<anonymous>
    promice = r.table("accounts").insert({
...
(16 additional frame(s) were not displayed)

ReqlDriverCompileError: Object field 'groupFields' may not be undefined

For Example:
In /routes/api/account.js there is a hierarchical endpoint that gets a single user by ID. '/id/:id/' This is fine because it returns only one user. However, /email/:email/, /userGroup/:userGroup/, /userGroup/:userGroup/name/:name and,/name/:name should be combined into a single search endpoint. For example:
example.com/api/account/search?userGroup=student&[email protected]&name=Student McStudentFace

If necessary add a GUID to each request to filter out duplicates.

Pass groups will have different means of receiving their pass, teachers will have it sent to their computers and notify them, the Library will not notify them, and it will use a kiosk.

Probably MIT or OSL-3.0

Depends on my mood. #

Features like:
Archive
Send activation email
Change password

Just simple gets and inserts and updates to the db

User Accounts

• Create
• Archive (Flips a bool in the db, can't login after set to true)
• Ban
  -- Think Of More

groupFields Student

• Set Schedule(new key: groupFields.schedule Will include student's schedule

groupFields to usergroups with pass groups assigned to them

• Set Limit
• Change Limit

Passes

• Add New pass to DB
• Cancel a pass (include who did it)
• [ ]

Tally

• Pass Tally to any pass group

make general perm groups in config and then apply them to the accounts.

• Set error message in schedule setter to suggest that one can check the no period box

• Add animation to successful schedule save

• update the My Passes card on Pass submit

• Load all teachers at once for the auto complete

• Show teacher's scheduled class during the pass request

• Denied passes should show as cancelled and should not be able to be reactivated

• If student cancels pass, it should be cancel not denied

• schedule definition should error if no schedule found