Skip to content

PAE - 159 setup stubs organisation registration accreditation #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

mohammeddebashi
Copy link
Contributor

@mohammeddebashi mohammeddebashi commented Aug 15, 2025

Ticket: PAE-159

Description

created stubs for signup, registration, accreditation


Please see the Pull Requests standards.

Copy link
Contributor

@nijk nijk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@nijk nijk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we've still got quite a bit to do by considering this PR holistically against the LLD, I think it needs more attention in the detail.

To avoid repetition, I won't repeat feedback across each endpoint, but every comment does need to be considered for each endpoint/test across the entire PR

name: 'Sarah Lee',
email: '[email protected]'
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't the payloads look more like DXT form data? Same for all endpoint tests

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we dont know what the forms contain, I think this will take time when the payload actually doesn't matter at this point and will only matter to the database not setting up the endpoint and giving back a response

Copy link
Contributor

@nijk nijk Aug 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We definitely know what the forms contain, we have links to the publicly accessible forms. We also know what data structure DXT sends to the api on submission. I'm suggesting that we make this data a closer representation to the DXT structure (as you've done in the postman collection) as it'll help with testing and future work, rather than doing a quick job now and having to update it later.

@@ -4,7 +4,8 @@ export const LOGGING_EVENT_CATEGORIES = {
HTTP: 'http',
PROXY: 'proxy',
SECRET: 'secret',
SERVER: 'server'
SERVER: 'server',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is dead code

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is being used on Start server, i dont understand how its dead code

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, my mistake. What's the difference between server and api then?

Copy link
Contributor Author

@mohammeddebashi mohammeddebashi Aug 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess server is related to server as it is starting or failing, but API would be related to methods relating to our api endpoints. Happy to get a different opinion what the category for the event would be

Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
22.2% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants