| Commit message (Collapse) | Author | Lines |
|
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
Co-authored-by: Bluenix <[email protected]>
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
Co-authored-by: Bluenix <[email protected]>
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
Adds the ability to specify who can edit forms using discord roles.
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
Adds a new property on forms to declare which roles are authorized to
access form responses.
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
Adds discord role support to the pre-existing scopes system to power
more complex access permissions.
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
We currently use WEBHOOK_ENABLED to determine whether user data should be stored to the db. However, when webhooking a form submission this config is ignored, and the user mention is always included if available.
This means that if a user login in using another form, and then submits an anonymous form with the same session, their name will be included in the webhook.
|
|
Note that it will make any existing form with an upper case letter impossible to access until its ID is changed, which shouldn't be the case in production according to @HassanAbouelela
|
|
|
|
Some of our deps don't have wheels for atm processors.
With Mac's M1 chips becomming more common, we should make it easier for those users to build our environments.
|
|
|
|
|
|
|