#658 Converted options to string #888

Merged
a22erigr merged 3 commits from #658-Options-dependenacy into team_2_week_5 2026-05-13 08:25:25 +00:00
Collaborator

Converting the options to a string stabilizes it and can be passed safely as a dependency.

Converting the options to a string stabilizes it and can be passed safely as a dependency.
Converting the options to a string stabilizes it and can be passed safely as a dependency.
c24danli changed title from Converted options to string to #658 Converted options to string 2026-05-12 10:56:36 +00:00
c24danli 2026-05-12 11:05:53 +00:00
Collaborator

Review on issue #885, PR #912

Whats done

Tested on Arch Linux, and Firefox

  • Compile the application to check that it works.
  • Check the logs that the warning is gone... it wasn't
    image
  • Inspected the file.
  • Run and make sure it still works by using the frontend.

Inspected the following files

  • frontend/src/features/utility/sharedFeatures.js
    • Indentation/code styling:
      • It follows prettier.
    • Naming convention
      • It is followed
    • Comments
      • Exist and are good
    • General code quality
      • Minus the error that is still there. It is good.

What needs to be done

After some discussion with @c24danli, the warning shown in the image needs to be addressed.
image

Also, fixing the merge conflict needs to be done.

Conclusion

For the moment, I don't recommend merging.

# Review on issue #885, PR #912 ## Whats done ### Tested on Arch Linux, and Firefox * Compile the application to check that it works. * Check the logs that the warning is gone... it wasn't ![image](/attachments/93340160-765e-4e61-82a3-3df02e1bb673) * Inspected the file. * Run and make sure it still works by using the frontend. ### Inspected the following files * **frontend/src/features/utility/sharedFeatures.js** * **Indentation/code styling**: * It follows prettier. * **Naming convention** * It is followed * **Comments** * Exist and are good * **General code quality** * Minus the error that is still there. It is good. ## What needs to be done After some discussion with @c24danli, the warning shown in the image needs to be addressed. ![image](/attachments/93340160-765e-4e61-82a3-3df02e1bb673) Also, fixing the merge conflict needs to be done. ## Conclusion For the moment, I don't recommend merging.
9.9 KiB
Author
Collaborator

Now the warning should not appear, as well as the API calls only executing when needed and no more.

Now the warning should not appear, as well as the API calls only executing when needed and no more.
Collaborator

bild

![bild](/attachments/d81e757f-8a2c-4a55-9276-0ddc6a74e180)
498 KiB
b24idalu left a comment
Collaborator

Review on #658

Whats done

Updated to make sure no warning will be shown and that the API is only executed when needed

Tested on Windows using Chrome & Firefox

  • App starts
    • The error is still there, per picture example.
    • Checked to make sure that the api calls only happen when needed.

Inspected following files

  • frontend/src/features/utility/sharedFeatures.js
    • Indentation/code styling
      • Follows prettier
    • CSS standard
      • Looks good
    • Naming convention
      • Looks good
    • Comments
      • Looks good
    • General code quality
      • Looks good other that the error still exists

What needs to be done

  • frontend/src/features/utility/sharedFeatures.js
    • Fix the error in the comment aboves picture.

Conclusion

  • Error needs to be fixed before merging
# Review on #658 ## Whats done Updated to make sure no warning will be shown and that the API is only executed when needed ### Tested on Windows using Chrome & Firefox + App starts + The error is still there, per picture example. + Checked to make sure that the api calls only happen when needed. ### Inspected following files + frontend/src/features/utility/sharedFeatures.js + Indentation/code styling + Follows prettier + CSS standard + Looks good + Naming convention + Looks good + Comments + Looks good + General code quality + Looks good other that the error still exists ## What needs to be done + frontend/src/features/utility/sharedFeatures.js + Fix the error in the comment aboves picture. ## Conclusion + Error needs to be fixed before merging
Author
Collaborator

@a22erigr wrote in #888 (comment):

bild

Could you please share the whole file with me because I am not getting this warning anymore

@a22erigr wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/pulls/888#issuecomment-10378: > [![bild](/attachments/d81e757f-8a2c-4a55-9276-0ddc6a74e180)](/Andras/BoundlessFlowCampus2K/attachments/d81e757f-8a2c-4a55-9276-0ddc6a74e180) Could you please share the whole file with me because I am not getting this warning anymore
Collaborator

@c22abdal wrote in #888 (comment):

@a22erigr wrote in #888 (comment):

bild

Could you please share the whole file with me because I am not getting this warning anymore

Its in util and from the branche

@c22abdal wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/pulls/888#issuecomment-10465: > @a22erigr wrote in #888 (comment): > > > [![bild](/attachments/d81e757f-8a2c-4a55-9276-0ddc6a74e180)](/Andras/BoundlessFlowCampus2K/attachments/d81e757f-8a2c-4a55-9276-0ddc6a74e180) > > Could you please share the whole file with me because I am not getting this warning anymore Its in util and from the branche
Author
Collaborator

@a22erigr wrote in #888 (comment):

@c22abdal wrote in #888 (comment):

@a22erigr wrote in #888 (comment):

bild

Could you please share the whole file with me because I am not getting this warning anymore

Its in util and from the branche

Yes thanks, i know that, i mean share the code because I am not getting the error. I want to check if the code is the same

@a22erigr wrote in https://git.webug.se/Andras/BoundlessFlowCampus2K/pulls/888#issuecomment-10482: > @c22abdal wrote in #888 (comment): > > > @a22erigr wrote in #888 (comment): > > > [![bild](/attachments/d81e757f-8a2c-4a55-9276-0ddc6a74e180)](/Andras/BoundlessFlowCampus2K/attachments/d81e757f-8a2c-4a55-9276-0ddc6a74e180) > > > > > > Could you please share the whole file with me because I am not getting this warning anymore > > Its in util and from the branche Yes thanks, i know that, i mean share the code because I am not getting the error. I want to check if the code is the same
a22erigr merged commit b5e6e6deaa into team_2_week_5 2026-05-13 08:25:25 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K!888
No description provided.